Mysql Enterprise Monitor vulnerabilitiesAnd the versions its exploited flaws hit.
Mysql Enterprise Monitor is made by Oracle. We track 58 published vulnerabilities in it, across 83 versions. 7 of them are on the list of flaws known to be exploited, the newest added on 12 May 2023. If you run Mysql Enterprise Monitor, check your version against the exploited flaws below and patch those first.
The most recent Mysql Enterprise Monitor flaw added to the known-exploited list is CVE-2016-8735, on 12 May 2023. We keep watching the known-exploited list.
Which versions of Mysql Enterprise Monitor do the exploited flaws hit?
Each exploited flaw lists the versions it affects, usually as ranges. "before 8.0.29" means every version up to, but not including, 8.0.29. Find your version, then patch.
- CVE-2016-8735Exploited list, 12 May 2023
Apache Tomcat Remote Code Execution Vulnerability
up to 3.2.8.22233.3.0 to 3.3.4.32473.4.0 to 3.4.2.4181 - CVE-2022-22963Exploited list, 25 Aug 2022
VMware Tanzu Spring Cloud Function Remote Code Execution Vulnerability
up to 8.0.29 - CVE-2022-22965Exploited list, 4 Apr 2022
Spring Framework JDK 9+ Remote Code Execution Vulnerability
before 8.0.29 - CVE-2017-12617Exploited list, 25 Mar 2022
Apache Tomcat Remote Code Execution Vulnerability
up to 3.3.6.32933.4.0 to 3.4.4.42264.0.0 to 4.0.0.5135 - CVE-2020-1938Exploited list, 3 Mar 2022
Apache Tomcat Improper Privilege Management Vulnerability
up to 4.0.128.0.0 to 8.0.20 - CVE-2020-17530Exploited list, 3 Nov 2021
Apache Struts Remote Code Execution Vulnerability
8.0.23 - CVE-2018-11776Exploited list, 3 Nov 2021
Apache Struts Remote Code Execution Vulnerability
up to 3.4.9.42374.0.0 to 4.0.6.52818.0.0 to 8.0.2.8191
Which Mysql Enterprise Monitor vulnerabilities are being exploited?
7 flaws are on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.
- 9.8Apache Tomcat Remote Code Execution Vulnerability
Apache Tomcat contains an unspecified vulnerability that allows for remote code execution if JmxRemoteLifecycleListener is used and an attacker can reach Java Management Extension (JMX) ports.
- 9.8VMware Tanzu Spring Cloud Function Remote Code Execution Vulnerability
When using routing functionality in VMware Tanzu's Spring Cloud Function, it is possible for a user to provide a specially crafted SpEL as a routing-expression that may result in remote code execution and access to...
- 9.8Spring Framework JDK 9+ Remote Code Execution Vulnerability
Spring MVC or Spring WebFlux application running on JDK 9+ may be vulnerable to remote code execution (RCE) via data binding.
- 8.1Apache Tomcat Remote Code Execution Vulnerability
When running Apache Tomcat, it is possible to upload a JSP file to the server via a specially crafted request.
- 9.8Apache Tomcat Improper Privilege Management Vulnerability
Apache Tomcat treats Apache JServ Protocol (AJP) connections as having higher trust than, for example, a similar HTTP connection.
- 9.8Apache Struts Remote Code Execution Vulnerability
Forced Object-Graph Navigation Language (OGNL) evaluation in Apache Struts, when evaluated on raw user input in tag attributes, can lead to remote code execution.
- 8.1Apache Struts Remote Code Execution Vulnerability
Apache Struts contains a vulnerability that allows for remote code execution under two circumstances.
Which Mysql Enterprise Monitor flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- >99%CVE-2021-45105Medium
Apache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3 and 2.3.1) did not protect from uncontrolled recursion from self-referential lookups.
- >99%
Apache Struts versions 2.3 to 2.3.34 and 2.5 to 2.5.16 suffer from possible Remote Code Execution when alwaysSelectFullNamespace is true (either by user or a plugin like Convention Plugin) and then: results are used...
- >99%
When running Apache Tomcat versions 9.0.0.M1 to 9.0.0, 8.5.0 to 8.5.22, 8.0.0.RC1 to 8.0.46 and 7.0.0 to 7.0.81 with HTTP PUTs enabled (e.g.
- >99%
In Spring Cloud Function versions 3.1.6, 3.2.2 and older unsupported versions, when using routing functionality it is possible for a user to provide a specially crafted SpEL as a routing-expression that may result in...
- >99%
A Spring MVC or Spring WebFlux application running on JDK 9+ may be vulnerable to remote code execution (RCE) via data binding.
- >99%
When using the Apache JServ Protocol (AJP), care must be taken when trusting incoming connections to Apache Tomcat.
- 97%CVE-2019-0230Critical
Apache Struts 2.0.0 to 2.5.20 forced double OGNL evaluation, when evaluated on raw user input in tag attributes, may lead to remote code execution.
- 96%
Forced OGNL evaluation, when evaluated on raw user input in tag attributes, may lead to remote code execution.
- 90%CVE-2017-5645Critical
In Apache Log4j 2.x before 2.8.2, when using the TCP socket server or UDP socket server to receive serialized log events from another application, a specially crafted binary payload can be sent that, when...
Running Mysql Enterprise Monitor? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 flaw being exploited affects software Acme tracks
Apache Tomcat contains an unspecified vulnerability that allows for remote code execution if JmxRemoteLifecycleListener is used and an attacker can reach Java Management Extension (JMX) ports. This CVE exists because this listener wasn't updated for consistency with the Oracle patched issues for CVE-2016-3427 which affected credential types.
- Matched to
- Mysql Enterprise Monitor on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 58 published vulnerabilities listed under the name Mysql Enterprise Monitor, across 83 versions. The most recent Mysql Enterprise Monitor flaw added to the known-exploited list is CVE-2016-8735, on 12 May 2023.
7 are on the list of flaws known to be exploited. The most recently added are CVE-2016-8735, CVE-2022-22963 and CVE-2022-22965.
Each flaw names its own versions, usually as ranges. The newest, CVE-2016-8735, affects up to 3.2.8.2223, 3.3.0 to 3.3.4.3247, 3.4.0 to 3.4.2.4181. The versions for every exploited flaw are listed on this page.
Create a Precursor Intelligence account and track Mysql Enterprise Monitor. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.