2023 - 06 MYLA V4 - 9 Cyber Security Bulletin
2023 - 06 MYLA V4 - 9 Cyber Security Bulletin
2023 - 06 MYLA V4 - 9 Cyber Security Bulletin
List of HIGH/CRITICAL known vulnerabilities on the MYLA® application software release 4.9.0
In computer security, a vulnerability is a weakness which allows an attacker to reduce a system's information
assurance. Vulnerability is the intersection of three elements: a system susceptibility or flaw, attacker access to
the flaw, and attacker capability to exploit the flaw. To exploit a vulnerability, an attacker must have at least one
applicable tool or technique that can connect to a system weakness.
Base
NESSUS CVSS Fixed in
Severity Title Description / Comment
plugin ID 3.1 MAESTRIA
score
NIST has determined that the protocol SSL3.0 is no longer acceptable for secure
communications.
port 3031 is used by vilink only locally. On Windows 10, Windows 2016 and
SSL Version 2 and 3
High 20007 7,5 Windows 2019, this port is blocked by the firewall. No
Protocol Detection
viLink will provide a fix in a future version.
A Java JMX agent running on the remote host is configured without SSL client and
password authentication. An unauthenticated, remote attacker can connect to
the JMX agent and monitor and manage the Java application that has enabled
the agent.
In the Myla 4.9 context, log4j is used to perform basic logging on files. There is
currently no vulnerabilities known on log4j 1.2.x for this usage. As a consequence
Apache Log4j Unsupported
Critical 156032 10,0 log4j 1.2.x is not considered as a Critical vulnerability in Myla 4.9 context. No
Version Detection
Log4j will be updated in a future version.
Myla have to be deployed in a secure lab with restricted access and strong
controls on the facility’s network, such as firewalls and endpoint protection in
Oracle Java JRE order to reduce the risk.
Critical Unsupported Version 55958 10,0 Yes
Detection The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Oracle Java SE Multiple In the Myla 4.9 context, with the validated design, these vulnerabilities cannot
Critical Vulnerabilities (June 2013 66932 9,8 happens. Yes
CPU)
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Myla have to be deployed in a secure lab with restricted access and strong
Oracle Java SE Multiple controls on the facility’s network, such as firewalls and endpoint protection in
Critical Vulnerabilities (October 70472 9,8 order to reduce the risk. Yes
2013 CPU)
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Myla have to be deployed in a secure lab with restricted access and strong
Oracle Java SE Multiple controls on the facility’s network, such as firewalls and endpoint protection in
Critical Vulnerabilities (January 71966 9,8 order to reduce the risk. Yes
2014 CPU)
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Myla have to be deployed in a secure lab with restricted access and strong
Oracle Java SE Multiple controls on the facility’s network, such as firewalls and endpoint protection in
Critical Vulnerabilities (April 2014 73570 9,8 order to reduce the risk. Yes
CPU)
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Myla have to be deployed in a secure lab with restricted access and strong
Oracle Java SE Multiple controls on the facility’s network, such as firewalls and endpoint protection in
Critical Vulnerabilities (July 2014 76532 9,8 order to reduce the risk. Yes
CPU)
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Myla have to be deployed in a secure lab with restricted access and strong
Oracle Java SE Multiple controls on the facility’s network, such as firewalls and endpoint protection in
Critical Vulnerabilities (October 78481 9,8 order to reduce the risk. Yes
2014 CPU)
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Myla have to be deployed in a secure lab with restricted access and strong
Oracle Java SE Multiple controls on the facility’s network, such as firewalls and endpoint protection in
Critical Vulnerabilities (January 80908 9,8 order to reduce the risk. Yes
2015 CPU) (POODLE)
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Myla have to be deployed in a secure lab with restricted access and strong
Oracle Java SE Multiple controls on the facility’s network, such as firewalls and endpoint protection in
Critical Vulnerabilities (April 2015 82820 9,8 order to reduce the risk. Yes
CPU) (FREAK)
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Myla have to be deployed in a secure lab with restricted access and strong
Oracle Java SE Multiple controls on the facility’s network, such as firewalls and endpoint protection in
Critical Vulnerabilities (July 2015 84824 9,8 order to reduce the risk. Yes
CPU) (Bar Mitzvah)
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Myla have to be deployed in a secure lab with restricted access and strong
Oracle Java SE Multiple controls on the facility’s network, such as firewalls and endpoint protection in
Critical Vulnerabilities (October 86542 9,8 order to reduce the risk. Yes
2015 CPU)
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Myla have to be deployed in a secure lab with restricted access and strong
Oracle Java SE Multiple controls on the facility’s network, such as firewalls and endpoint protection in
Critical Vulnerabilities (January 88045 9,8 order to reduce the risk. Yes
2016 CPU) (SLOTH)
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Myla have to be deployed in a secure lab with restricted access and strong
Oracle Java SE Multiple controls on the facility’s network, such as firewalls and endpoint protection in
Critical Vulnerabilities (April 2016 90625 9,6 order to reduce the risk. Yes
CPU)
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Myla have to be deployed in a secure lab with restricted access and strong
Oracle Java SE Multiple controls on the facility’s network, such as firewalls and endpoint protection in
Critical Vulnerabilities (July 2016 92516 9,6 order to reduce the risk. Yes
CPU)
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Myla have to be deployed in a secure lab with restricted access and strong
Oracle Java SE Multiple controls on the facility’s network, such as firewalls and endpoint protection in
Critical Vulnerabilities (October 94138 9,6 order to reduce the risk. Yes
2016 CPU)
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Myla have to be deployed in a secure lab with restricted access and strong
Oracle Java SE Multiple controls on the facility’s network, such as firewalls and endpoint protection in
Critical Vulnerabilities (October 103963 9,8 order to reduce the risk. Yes
2017 CPU)
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Oracle Java SE 1.7.0_241 / Myla have to be deployed in a secure lab with restricted access and strong
1.8.0_231 / 1.11.0_5 / controls on the facility’s network, such as firewalls and endpoint protection in
Critical 1.13.0_1 Multiple 130011 9,8 order to reduce the risk. Yes
Vulnerabilities (Oct 2019
CPU) (Windows) The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Myla have to be deployed in a secure lab with restricted access and strong
Oracle Java SE Multiple controls on the facility’s network, such as firewalls and endpoint protection in
Critical Vulnerabilities (July 2017 101843 9,6 order to reduce the risk. Yes
CPU)
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Myla have to be deployed in a secure lab with restricted access and strong
Oracle Java SE Multiple controls on the facility’s network, such as firewalls and endpoint protection in
Critical Vulnerabilities (January 96628 9,6 order to reduce the risk. Yes
2017 CPU) (SWEET32)
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Myla have to be deployed in a secure lab with restricted access and strong
Oracle Java SE Multiple controls on the facility’s network, such as firewalls and endpoint protection in
Critical Vulnerabilities (July 2018 111163 9,0 order to reduce the risk. Yes
CPU)
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Myla have to be deployed in a secure lab with restricted access and strong
Oracle Java SE Multiple controls on the facility’s network, such as firewalls and endpoint protection in
Critical Vulnerabilities (October 118228 9,0 order to reduce the risk. Yes
2018 CPU)
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Oracle Java SE 1.7.0_221 / Myla have to be deployed in a secure lab with restricted access and strong
1.8.0_211 / 1.11.0_3 / controls on the facility’s network, such as firewalls and endpoint protection in
Critical 1.12.0_1 Multiple 124198 9,0 order to reduce the risk. Yes
Vulnerabilities (Apr 2019
CPU) The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Myla have to be deployed in a secure lab with restricted access and strong
Oracle Java SE Hotspot JSR controls on the facility’s network, such as firewalls and endpoint protection in
High 90828 8,1 order to reduce the risk. Yes
292 Method Handles RCE
Oracle Java SE 1.7.0_321 / Myla have to be deployed in a secure lab with restricted access and strong
1.8.0_311 / 1.11.0_13 / controls on the facility’s network, such as firewalls and endpoint protection in
High 1.17.0_1 Multiple 154344 8,6 order to reduce the risk. Yes
Vulnerabilities (October
2021 CPU) The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Myla have to be deployed in a secure lab with restricted access and strong
Azul Zulu Java Multiple controls on the facility’s network, such as firewalls and endpoint protection in
High Vulnerabilities (2021-10- 154381 8,6 order to reduce the risk. Yes
19)
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Myla have to be deployed in a secure lab with restricted access and strong
Oracle Java SE Multiple controls on the facility’s network, such as firewalls and endpoint protection in
High Vulnerabilities (January 106190 8,3 order to reduce the risk. Yes
2018 CPU)
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Oracle Java SE 1.7.0_251 / Myla have to be deployed in a secure lab with restricted access and strong
1.8.0_241 / 1.11.0_6 / controls on the facility’s network, such as firewalls and endpoint protection in
High 1.13.0_2 Multiple 132992 8,1 order to reduce the risk. Yes
Vulnerabilities (Jan 2020
CPU) The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Myla have to be deployed in a secure lab with restricted access and strong
Oracle Java SE Multiple controls on the facility’s network, such as firewalls and endpoint protection in
High Vulnerabilities (April 2018 109202 7,4 order to reduce the risk. Yes
CPU)
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Myla have to be deployed in a secure lab with restricted access and strong
Oracle Java SE Multiple controls on the facility’s network, such as firewalls and endpoint protection in
High Vulnerabilities (April 2017 99588 8,3 order to reduce the risk. Yes
CPU)
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Oracle Java SE 1.7.0_311 / Myla have to be deployed in a secure lab with restricted access and strong
1.8.0_301 / 1.11.0_12 / controls on the facility’s network, such as firewalls and endpoint protection in
High 1.16.0_2 Multiple 152020 7,5 order to reduce the risk. Yes
Vulnerabilities (July 2021
CPU) The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Myla have to be deployed in a secure lab with restricted access and strong
Azul Zulu Java Multiple controls on the facility’s network, such as firewalls and endpoint protection in
High Vulnerabilities (2021-07- 153989 7,5 order to reduce the risk. Yes
20)
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
In the Myla 4.9 context, with the validated design, this vulnerability cannot
Apache Tomcat 9.0.0.M1 <
High 138098 7,5 happens. Yes
9.0.36 DoS
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Apache Tomcat 9.x < Myla have to be deployed in a secure lab with restricted access and strong
High 9.0.40 Information 144050 7,5 controls on the facility’s network, such as firewalls and endpoint protection in Yes
Disclosure order to reduce the risk.
Apache Tomcat 9.0.0.M1 < In the Myla 4.9 context, with the validated design, theses vulnerabilities cannot
High 9.0.43 Multiple 147164 7,5 happens. Yes
Vulnerabilities
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
In the Myla 4.9 context, with the validated design, this vulnerability cannot
Apache Tomcat 9.0.0 < happens.
High 9.0.35 Remote Code 136806 7,0 Yes
Execution The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
* CVE-2017-12626: The POI library is used in BCI Link for a feature that export
Excel files. This feature is not enabled in the Myla context.
Apache POI < 3.17 In the Myla 4.9 context, with the validated design, this vulnerability cannot
High Multiple DoS 106717 7,5 happens. Yes
Vulnerabilities
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Apache Log4j 1.2 In the Myla 4.9 context, with the validated design, these vulnerabilities cannot
JMSAppender Remote
High 156103 7,5 happens. No
Code Execution (CVE-
2021-4104) Log4j will be updated in a future version.
Myla have to be deployed in a secure lab with restricted access and strong
Oracle Java SE Multiple controls on the facility’s network, such as firewalls and endpoint protection in
High Vulnerabilities (April 2022 159975 7,5 order to reduce the risk. Yes
CPU) deprecated
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
In the Myla 4.9 context, with the validated design, these vulnerabilities cannot
Apache Tomcat 9.0.13 <
High 160894 7,5 happens. Yes
9.0.63 vulnerability
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
The service “Agentless Management Service” from HP contains space in the path
and this patch is not enclosed in quotes.
Myla have to be deployed in a secure lab with restricted access and strong
Oracle Java JDK / JRE 6 < controls on the facility’s network, such as firewalls and endpoint protection in
Critical Update 43 Remote Code 65050 N/A order to reduce the risk. Yes
Execution (Windows)
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Myla have to be deployed in a secure lab with restricted access and strong
Oracle Java SE Multiple controls on the facility’s network, such as firewalls and endpoint protection in
Critical Vulnerabilities (February 64790 N/A order to reduce the risk. Yes
2013 CPU Update 1)
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Oracle Java SE 1.7.0_261 / Myla have to be deployed in a secure lab with restricted access and strong
1.8.0_251 / 1.11.0_7 / controls on the facility’s network, such as firewalls and endpoint protection in
High 1.14.0_1 Multiple 135592 8,3 order to reduce the risk. Yes
Vulnerabilities (Apr 2020
CPU) The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Myla have to be deployed in a secure lab with restricted access and strong
SSL Medium Strength controls on the facility’s network, such as firewalls and endpoint protection in
High Cipher Suites Supported 42873 7,5 order to reduce the risk. Yes
(SWEET32)
The vulnerability is fixed in MAESTRIA 5.0.0 and upper with the default
configuration.
Oracle Java SE 1.7.0_271 / Myla have to be deployed in a secure lab with restricted access and strong
1.8.0_261 / 1.11.0_8 / controls on the facility’s network, such as firewalls and endpoint protection in
High 1.14.0_2 Multiple 138522 8,3 order to reduce the risk. Yes
Vulnerabilities (Jul 2020
CPU) The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Myla have to be deployed in a secure lab with restricted access and strong
Apache Shiro < 1.4.2 controls on the facility’s network, such as firewalls and endpoint protection in
High 161730 7,5 order to reduce the risk. Yes
Padding Attack
Myla have to be deployed in a secure lab with restricted access and strong
Apache Shiro < 1.6.0 controls on the facility’s network, such as firewalls and endpoint protection in
High 161733 7,5 order to reduce the risk. Yes
Authentication Bypass
Myla have to be deployed in a secure lab with restricted access and strong
Apache Shiro < 1.5.2 controls on the facility’s network, such as firewalls and endpoint protection in
Critical 161732 9,8 order to reduce the risk. Yes
Authentication Bypass
Myla have to be deployed in a secure lab with restricted access and strong
Apache Shiro < 1.7.0 controls on the facility’s network, such as firewalls and endpoint protection in
Critical 161694 9,8 order to reduce the risk. Yes
Authentication Bypass
Myla have to be deployed in a secure lab with restricted access and strong
Apache Shiro < 1.7.1 controls on the facility’s network, such as firewalls and endpoint protection in
Critical 161693 9,8 order to reduce the risk. Yes
Authentication Bypass
Myla have to be deployed in a secure lab with restricted access and strong
Apache Shiro < 1.2.5 controls on the facility’s network, such as firewalls and endpoint protection in
High Default Cipher Key (CVE- 159764 8,1 order to reduce the risk. Yes
2016-4437)
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Myla have to be deployed in a secure lab with restricted access and strong
Apache Shiro < 1.5.3 controls on the facility’s network, such as firewalls and endpoint protection in
Critical 161727 9,8 order to reduce the risk. Yes
Authentication Bypass
Myla have to be deployed in a secure lab with restricted access and strong
Apache Tomcat 9.0.0.M1 < controls on the facility’s network, such as firewalls and endpoint protection in
High 9.0.30 Privilege Escalation 132419 7,5 order to reduce the risk. Yes
Vulnerability
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Myla have to be deployed in a secure lab with restricted access and strong
Oracle Java SE Multiple controls on the facility’s network, such as firewalls and endpoint protection in
High Vulnerabilities (July 2022 163304 7,5 order to reduce the risk. Yes
CPU)
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Myla have to be deployed in a secure lab with restricted access and strong
Azul Zulu Java Multiple controls on the facility’s network, such as firewalls and endpoint protection in
High Vulnerabilities (2022-07- 163301 7,5 order to reduce the risk. Yes
19)
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Myla have to be deployed in a secure lab with restricted access and strong
Oracle Java SE Multiple controls on the facility’s network, such as firewalls and endpoint protection in
High Vulnerabilities (April 2022 161241 7,5 order to reduce the risk. Yes
CPU)
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
In the Myla 4.9 context, with the validated design, this vulnerability cannot
CGI Generic SQL Injection
High 42424 N/A happens. Yes
(blind)
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Myla have to be deployed in a secure lab with restricted access and strong
Azul Zulu Java Multiple controls on the facility’s network, such as firewalls and endpoint protection in
High Vulnerabilities (2022-04- 159902 7,5 order to reduce the risk. Yes
19)
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Myla have to be deployed in a secure lab with restricted access and strong
Apache Tomcat 9.0.0-M1 < controls on the facility’s network, such as firewalls and endpoint protection in
High 9.0.68 Request Smuggling 166906 7,5 order to reduce the risk. Yes
Vulnerability
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
bioMérieux components does not use the vulnerable feature of the common text
library.
Apache Commons Text
1.5.x < 1.10.0 Remote In the Myla 4.9 context, with the validated design, this vulnerability cannot
Critical 166250 9,8 happens. Yes
Code Execution (CVE-
2022-42889)
The vulnerability is fixed in MAESTRIA 5.0.0 and upper.
Myla have to be deployed in a secure lab with restricted access and strong
Apache Tomcat 9.0.0.M1 <
High 171657 7,5 controls on the facility’s network, such as firewalls and endpoint protection in Yes
9.0.71 order to reduce the risk.
Myla have to be deployed in a secure lab with restricted access and strong
controls on the facility’s network, such as firewalls and endpoint protection in
Apache 2.4.x < 2.4.56
Critical 172186 9,1 order to reduce the risk. No
Multiple Vulnerabilities
The vulnerability will be fixed in a future version.
Critical PuTTY suite N/A 9,8 In the Myla 4.9 context, with the validated design, these vulnerabilities cannot Yes
happens in routine usage.
Myla have to be deployed in a secure lab with restricted access and strong
controls on the facility’s network, such as firewalls and endpoint protection in
order to reduce the risk.
7zip cannot be used remotely. There is no routine users connected to the Myla
server. bioMérieux support team already have the Administrator privilege and
High 7-Zip N/A 8,8 customer IT (if needed) also have this privilege. No
In the Myla context, this vulnerability does not add any risk.
* CVE-2019-16294
High Notepad++ (32-bit x86) N/A 7,8 In the Myla 4.9 context, with the validated design, these vulnerabilities cannot Yes
happens in routine usage.
Critical VLC media player N/A 9,8 viLink will provide a fix in a future version. No
viLink will provide a fix in a future version.
teamviewer:TeamViewer,
teamviewer:TeamViewer
Critical 11 Host, N/A 9,8 No
teamviewer:TeamViewer
11 Host (MSI Wrapper)
FIX IS AVAILABLE (via VILINK) : VITEK MS - Cyber Security Patch-OS 01 - See GCS INFO 3080
B Critical HP System Management Homepage < 7.4.1 Single Sign On Buffer Overflow RCE Yes -(1) -(1) -(1)
FIX IS AVAILABLE (via VILINK) : MYLA V4.1 - Cyber Security Patch-OS 02 - See GCS INFO 2795
C Critical Microsoft Internet Explorer Unsupported Version Detection Yes -(1) -(1) -(1)
FIX IS AVAILABLE (via VILINK) : MYLA V4.3 - Cyber Security Patch-OS 03 - See GCS INFO 2967
FIX IS AVAILABLE SINCE APRIL 2016 WITH FCA 2853 regarding MYLA Patch Core Version 4.3.
E Critical Microsoft SQL Server Unsupported Version Detection Yes -(1) -(1) -(1)
FIX IS AVAILABLE SINCE JANUARY 2017: VITEK MS - Cyber Security Patch OS-3 – See GCS INFO 3268
F High Foxit Reader < 7.2 Multiple Vulnerabilities Yes -(1) -(1) -(1)
FIX IS AVAILABLE (via VILINK) : MYLA V4.4 - Cyber Security Patch-OS 04 – See GCS INFO 3248
G High 7-Zip < 16.00 Multiple Vulnerabilities Yes -(1) -(1) -(1)
FIX IS AVAILABLE (via VILINK) : MYLA V4.4 - Cyber Security Patch-OS 04 – See GCS INFO 3248
FIX IS AVAILABLE (via VILINK) : MYLA V4.1 - Cyber Security Patch-OS 02 - See GCS INFO 2795
I High MS13-081: Vulnerabilities in Windows Kernel-Mode Drivers Could Allow Remote Code Execution (2870008) Yes -(1) -(1) -(1)
Some security scanners erroneously report this vulnerability even after installation of the relevant
Microsoft Security Update MS13-081: the vulnerable driver in system32/drivers will be seen as updated
only after a relevant USB/Serial device (e.g. USB GPRS Modem) is plugged.
J High MS15-124: Cumulative Security Update for Internet Explorer (3116180) Yes -(1) -(1) -(1)
FIX IS AVAILABLE (via VILINK) : MYLA V4.3 - Cyber Security Patch-OS 03 - See GCS INFO 2967
K High OpenSSL 1.0.1 < 1.0.1s Multiple Vulnerabilities (DROWN) Yes -(1) -(1) -(1)
FIX IS AVAILABLE (via VILINK) : MYLA V4.3 - Cyber Security Patch-OS 03 - See GCS INFO 2967
L Critical KB4022722: Windows 7 and Windows 2008 R2 June 2017 Cumulative Update Yes -(1) -(1) -(1)
FIX IS AVAILABLE (via VILINK) : MYLA V4.5.1 - Launch with Smart Updater Installation - See MAR 3738
M High MS11-025 on Windows 10 PC only: Vulnerability in Microsoft Foundation Class (MFC) Library Could Allow Not Yes Not -(1)
Remote Code Execution (2500212). present present
FIX IS AVAILABLE (via VILINK) : MYLA 4.6.1 – Launched with Smart Updater Installation – See MAR 4071
N Critical Critical “7-Zip < 18.05 Memory Corruption Arbitrary Code Execution” Yes Yes Yes -(1)
FIX IS AVAILABLE (via VILINK) : MYLA 4.7.0 – Launched with Smart Updater Installation – GCS INFO 4236
and MAR 4438 (Myla 4.7.1)
P Critical Some vulnerability linked to apache 2.4.23 were not reported by NESSUS: See Yes Yes Yes -(1)
High https://nvd.nist.gov/vuln/search/results?form_type=Advanced
&cves=on&cpe_version=cpe%3a%2fa%3aapache%3ahttp_server%3a2.4.23 for more details.
FIX IS AVAILABLE (via VILINK): MYLA 4.7.1 – Launched with Smart Updater Installation – GCS INFO 4236
and MAR 4438
Q High MS16-136: Security Update for SQL Server (3199641): This vulnerability is on VitekMS+ Saramis. Yes No(2) Yes -(1)
FIX IS AVAILABLE: See VITEK MS – Cyber Security Patch OS-4 (GCS INFO 4380)
R High MS11-025: Vulnerability in Microsoft Foundation Class (MFC) Library Could Allow Remote Code No(3) No(2) Yes -(1)
Execution (2500212): This vulnerability is on VitekMS+ Saramis.
FIX IS AVAILABLE: See VITEK MS – Cyber Security Patch OS-4 (GCS INFO 4380)
S High Java JMX Agent Insecure Configuration: This vulnerability is on VitekMS and can allow a remote attacker Yes Yes Yes -(1)
to monitor and manage (start/stop/modify) the VitekMS application running on the Myla server.
FIX IS AVAILABLE: See VITEK MS – Cyber Security Patch OS-4 (GCS INFO 4380)
FIX IS AVAILABLE (via VILINK): MYLA 4.8.0 – Installed with Smart Updater Installation – GCS-INFO 4687
U High “Insecure Windows Service Permissions”: Windows service are now launched by using specific service No Yes No -(1)
account with limited ACL.
FIX IS AVAILABLE (via VILINK): MYLA 4.8.0 – Installed with Smart Updater Installation – GCS-INFO 4687
V Critical Adobe Flash Player Unsupported Version Detection: Adobe Flash Player is no more supported, so no new N/A(4) Yes No -(1)
security patches for the product will be released by the vendor. As a result, it is likely to contain security
vulnerabilities.
W Critical Microsoft Windows 7 / Server 2008 R2 Unsupported Version Detection Yes No No -(1)
X High “SSL Version 2 and 3 Protocol Detection” on port 9200 N/A(4) Yes Yes -(1)
Y High PostgreSQL 9.6.x < 9.6.20 Multiple Vulnerabilities N/A(4) Yes Yes -(1)
AA Critical Apache 2.4.x < 2.4.46 Multiple Vulnerabilities (NESSUS plugin 139574) N/A(4) Yes Yes Yes
AB Critical Apache 2.4.x >= 2.4.7 / < 2.4.52 Forward Proxy DoS / SSRF (NESSUS plugin 156255) N/A(4) Yes Yes Yes
AC High Apache >= 2.4.17 < 2.4.49 mod_http2 (NESSUS plugin 153585) N/A(4) Yes Yes Yes
AD High Apache >= 2.4.30 < 2.4.49 mod_proxy_uwsgi (NESSUS plugin 153586) N/A(4) Yes Yes Yes
AF High Apache 2.4.x < 2.4.48 Vulnerability (NESSUS plugin 150244) N/A(4) Yes Yes Yes
AG Critical Apache 2.4.x < 2.4.47 Multiple Vulnerabilities (NESSUS plugin 150280) N/A(4) Yes Yes Yes
AH Critical Apache < 2.4.49 Multiple Vulnerabilities (NESSUS plugin 153584) N/A(4) Yes Yes Yes
AI Critical Apache < 2.4.49 Multiple Vulnerabilities (NESSUS plugin 153583) N/A(4) Yes Yes Yes
AJ Critical Apache 2.4.x < 2.4.41 Multiple Vulnerabilities (NESSUS plugin 128033) N/A(4) Yes Yes Yes
AK Critical Apache 2.4.x < 2.4.54 Multiple Vulnerabilities (NESSUS plugin 161948) N/A(4) Yes Yes Yes
AL Critical Apache 2.4.x < 2.4.53 Multiple Vulnerabilities (NESSUS plugin 158900) N/A(4) Yes Yes Yes
(1): Myla was available not available on this Operating System when the vulnerability was found.
(2): VitekMS+ Saramis is not supported on Myla PC
2023 - 06 MYLA V4_9 Cyber Security Bulletin.doc 32/36
(3): Not reported by Nessus on our platform
(4): Windows 2008 not monitored anymore since May 2020
As specified in the User Manual, bioMérieux highly recommends to perform qualification procedure after any security updates.
Yours Sincerely,
System Development
La Balme
Cybersecurity patches
Cybersecurity patch 1 to 4
Not available as a standalone package. Included in Myla 4.5.1 Smart Updater and following.
Not available as a standalone package. Included in Myla 4.6.1 Smart Updater and following.
Not available as a standalone package. Included in Myla 4.7 Smart Updater and following.
Note: Since Myla 4.7.0 all the communication between the browser and the Myla server are done in https (that is
to say, the communication are encrypted).
Not available as a standalone package. Included in Myla 4.7.1 Smart Updater and following.
Not available as a standalone package. Included in Myla 4.8.0 Smart Updater and following.
Other improvements:
• Several component update including:
o apache http server updated to version 2.4.39
o postgreSQL updated to version 12.5
• More secure management of the bmx_admin account password
Remote BCI GUI <-> BCI on Myla Server BCI Connect: Yes
BCI Link: No
The communication between Vitek2 9.01 (and above) and Myla can
be encrypted (See service documentation for instructions)
The communication between Virtuo R3.0 (and above) and Myla can
be encrypted (See service documentation for instructions)