Vulnerability Database

328,409

Total vulnerabilities in the database

Vulnerabilities for products matching "mysql_enterprise_monitor"

Found 1 matching product.

You can search for specific versions with /product/mysql_enterprise_monitor/1.2.3

oracle / mysql_enterprise_monitor

58 vulnerabilities found
Title Severity Exploit Date Affected Version
Medium April 14, 2022 4/14/22
<= 8.0.29
Critical April 1, 2022 4/1/22
<= 8.0.29
Critical April 1, 2022 4/1/22
< 8.0.29
High February 24, 2022 2/24/22
<= 8.0.29
High February 24, 2022 2/24/22
<= 8.0.29
Medium February 24, 2022 2/24/22
<= 8.0.29
Medium February 24, 2022 2/24/22
<= 8.0.29
High January 27, 2022 1/27/22
<= 8.0.29
High January 18, 2022 1/18/22
<= 8.0.29
Critical January 18, 2022 1/18/22
<= 8.0.29
High January 18, 2022 1/18/22
<= 8.0.29
Medium December 18, 2021 12/18/21
<= 8.0.29
High December 14, 2021 12/14/21
<= 8.0.29
Medium October 26, 2021 10/26/21
<= 8.0.29
Medium October 26, 2021 10/26/21
<= 8.0.29
Critical August 24, 2021 8/24/21
<= 8.0.25
High August 24, 2021 8/24/21
<= 8.0.25
Medium July 12, 2021 7/12/21
<= 8.0.25
High May 27, 2021 5/27/21
<= 8.0.25
High March 25, 2021 3/25/21
<= 8.0.23
High March 1, 2021 3/1/21
<= 8.0.23
High March 1, 2021 3/1/21
<= 8.0.23
High February 23, 2021 2/23/21
<= 8.0.25
Medium February 16, 2021 2/16/21
< 8.0.23
Critical December 11, 2020 12/11/20
== 8.0.23
High December 3, 2020 12/3/20
< 8.0.23
Medium November 24, 2020 11/24/20
<= 8.0.30
Medium September 19, 2020 9/19/20
<= 8.0.22
== 8.0.23
Critical September 14, 2020 9/14/20
<= 8.0.23
High September 14, 2020 9/14/20
<= 8.0.23
High July 14, 2020 7/14/20
<= 8.0.21
High July 14, 2020 7/14/20
<= 8.0.21
High June 26, 2020 6/26/20
<= 8.0.21
High May 20, 2020 5/20/20
<= 8.0.21
High April 21, 2020 4/21/20
<= 4.0.12
>= 8.0.0 <= 8.0.20
Critical February 24, 2020 2/24/20
<= 4.0.12
>= 8.0.0 <= 8.0.20
Low February 24, 2020 2/24/20
<= 4.0.12
>= 8.0.0 <= 8.0.20
Low February 24, 2020 2/24/20
>= 8.0.0 <= 8.0.20
>= 4.0.0 <= 4.0.12
Medium January 17, 2020 1/17/20
>= 8.0.0 <= 8.0.20
>= 4.0.0 <= 4.0.12
High December 23, 2019 12/23/19
<= 4.0.11.5331
>= 8.0.0 <= 8.0.18.1217
Critical December 20, 2019 12/20/19
<= 8.0.29
Medium December 6, 2019 12/6/19
<= 4.0.12
>= 8.0.0 <= 8.0.20
Medium February 27, 2019 2/27/19
>= 8.0.0 <= 8.0.14
<= 4.0.8
High October 18, 2018 10/18/18
<= 4.0.12
>= 8.0.0 <= 8.0.20
High August 22, 2018 8/22/18
<= 3.4.9.4237
>= 8.0.0 <= 8.0.2.8191
>= 4.0.0 <= 4.0.6.5281
Medium June 25, 2018 6/25/18
<= 3.4.9.4237
>= 8.0.0 <= 8.0.2.8191
>= 4.0.0 <= 4.0.6.5281
High June 25, 2018 6/25/18
>= 3.4.10 <= 4.0.6.5281
<= 3.4.9.4237
>= 4.0.7 <= 8.0.2.8191
High May 11, 2018 5/11/18
<= 8.0.2.8191
Medium October 19, 2017 10/19/17
== 3.2.0
== 3.2.1
== 3.2.2
== 3.2.3
== 3.2.4
== 3.2.5
== 3.2.6
== 3.2.7
== 3.2.8
== 3.2.8.2223
== 3.3.0
== 3.3.1
== 3.3.2
== 3.3.3
== 3.3.4
== 3.3.4.3247
== 3.4.0
== 3.4.1
== 3.4.2
== 3.4.2.4181
High October 4, 2017 10/4/17
>= 4.0.0 <= 4.0.0.5135
>= 3.4.0 <= 3.4.4.4226
<= 3.3.6.3293

Frequently Asked Questions

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.

Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.

Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.