How should we interpret CVSS severity scores?

CVSS estimates technical severity, but it does not automatically equal business risk. Prioritize using context like internet exposure, asset criticality, known exploitation, 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.

Vulnerability Database

Q: What is a Vulnerability (CVE) and why does it matter?

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.

Q: What's the difference between a vulnerability, an exploit, and a zero-day?

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. Risk increases sharply when exploitation becomes reliable or widespread.

Q: Why do vulnerabilities keep reappearing in our environment?

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.

Q: How do we prioritize remediation without burning out the team?

Use a 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 so remediation is steady, not reactive.

Q: How can SynScan help reduce vulnerability risk over time?

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.

328,409

Total vulnerabilities in the database

Vulnerabilities for products matching "mysql"

Found 6 matching products. Filters apply to all results.

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

oracle / mysql

1326 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2004-0457	Low	September 28, 2004 9/28/04	<= 4.0.20
CVE-2004-0388	Low	June 1, 2004 6/1/04	== 5.0.33
CVE-2004-0381	Low	May 4, 2004 5/4/04	== 3.20.32a == 3.22.26 == 3.22.27 == 3.22.28 == 3.22.29 == 3.22.30 == 3.22.32 == 3.23.2 == 3.23.3 == 3.23.5 == 3.23.8 == 3.23.9 == 3.23.10 == 3.23.22 == 3.23.23 == 3.23.24 == 3.23.25 == 3.23.26 == 3.23.27 == 3.23.28-gamma == 3.23.28 == 3.23.29 == 3.23.30 == 3.23.31 == 3.23.32 == 3.23.33 == 3.23.34 == 3.23.36 == 3.23.37 == 3.23.38 == 3.23.39 == 3.23.40 == 3.23.41 == 3.23.42 == 3.23.43 == 3.23.44 == 3.23.45 == 3.23.46 == 3.23.47 == 3.23.48 == 3.23.49 == 3.23.50 == 3.23.51 == 3.23.52 == 3.23.53 == 3.23.53a == 3.23.54 == 3.23.54a == 3.23.55 == 3.23.56 == 3.23.58 == 4.0.0 == 4.0.1 == 4.0.2 == 4.0.3 == 4.0.4 == 4.0.5 == 4.0.5a == 4.0.6 == 4.0.7 == 4.0.7-gamma == 4.0.8-gamma == 4.0.8 == 4.0.9 == 4.0.9-gamma == 4.0.10 == 4.0.11-gamma == 4.0.11 == 4.0.12 == 4.0.13 == 4.0.14 == 4.0.15 == 4.0.18 == 4.1.0-alpha
CVE-2003-1331	Low	December 31, 2003 12/31/03	<= 4.0.9
CVE-2003-1480	Low	December 31, 2003 12/31/03	== 3.20 == 3.20.32a == 3.21 == 3.22 == 3.22.26 == 3.22.27 == 3.22.28 == 3.22.29 == 3.23.10 == 3.23.22 == 3.23.24 == 3.23.28-gamma == 3.23.3 == 3.23.8 == 3.22.30 == 3.22.32 == 3.23.5 == 3.23.25 == 3.23.26 == 3.23.27 == 3.23.28 == 3.23.4 == 3.23.2 == 3.23.23 == 3.23.29 == 3.23.9 == 3.23.36 == 3.23.38 == 3.23.44 == 3.23.46 == 3.23.50 == 3.23.52 == 4.0.0 == 4.0.8-gamma == 3.23.31 == 3.23.32 == 3.23.33 == 3.23.34 == 3.23.47 == 3.23.48 == 3.23.49 == 4.0.1 == 4.0.2 == 4.0.3 == 4.0.5a == 3.23.39 == 3.23.40 == 3.23.41 == 3.23.42 == 3.23.53a == 3.23.54 == 3.23.54a == 3.23.55 == 3.23.30 == 3.23.35 == 3.23.37 == 3.23.43 == 3.23.45 == 3.23.51 == 3.23.53 == 3.23.56 == 4.0.7-gamma == 4.0.11-gamma == 4.1.0-alpha == 4.0.9-gamma
CVE-2003-0780	High	September 22, 2003 9/22/03	== 3.23 == 3.23.2 == 3.23.3 == 3.23.4 == 3.23.5 == 3.23.25 == 3.23.26 == 3.23.32 == 3.23.33 == 3.23.22 == 3.23.28-gamma == 3.23.29 == 3.23.9 == 3.23.10 == 3.23.27 == 3.23.28 == 3.23.34 == 3.23.36 == 3.23.8 == 3.23.23 == 3.23.24 == 3.23.30 == 3.23.31 == 3.23.40 == 3.23.41 == 3.23.48 == 3.23.49 == 3.23.54a == 3.23.55 == 4.0.5 == 4.0.5a == 4.0.6 == 3.23.37 == 3.23.38 == 3.23.44 == 3.23.45 == 3.23.52 == 3.23.53 == 4.0.0 == 4.0.2 == 4.0.8 == 4.0.8-gamma == 3.23.42 == 3.23.43 == 3.23.50 == 3.23.51 == 3.23.56 == 4.0.7 == 4.0.7-gamma == 3.23.39 == 3.23.46 == 3.23.47 == 3.23.53a == 3.23.54 == 4.0.1 == 4.0.3 == 4.0.4 == 4.0.9 == 4.0.9-gamma == 4.0.11 == 4.0.11-gamma == 4.0.14 == 4.0.12 == 4.0.13 == 4.1.0-alpha == 4.0.10
CVE-2003-0150	High	March 24, 2003 3/24/03	== 3.23.52 == 3.23.53 == 3.23.53a == 3.23.54 == 3.23.54a == 3.23.55
CVE-2003-0073	Medium	February 19, 2003 2/19/03	== 3.23.31 == 3.23.36 == 3.23.41 == 3.23.47 == 3.23.52 == 3.23.53 == 3.23.54 == 3.23.54a
CVE-2002-1809	High	December 31, 2002 12/31/02	== 3.23.2 == 3.23.3 == 3.23.4 == 3.23.5 == 3.23.8 == 3.23.9 == 3.23.10 == 3.23.23 == 3.23.24 == 3.23.25 == 3.23.26 == 3.23.27 == 3.23.28 == 3.23.29 == 3.23.30 == 3.23.31 == 3.23.34 == 3.23.36 == 3.23.37 == 3.23.38 == 3.23.39 == 3.23.40 == 3.23.41 == 3.23.42 == 3.23.43 == 3.23.44 == 3.23.45 == 3.23.46 == 3.23.47 == 3.23.48 == 3.23.49 == 3.23.50 == 3.23.51 == 3.23.52
CVE-2002-1921	High	December 31, 2002 12/31/02	== 3.20.32a == 3.22.26 == 3.22.27 == 3.22.28 == 3.22.29 == 3.22.30 == 3.22.32 == 3.23.2 == 3.23.3 == 3.23.4 == 3.23.5 == 3.23.8 == 3.23.9 == 3.23.10 == 3.23.23 == 3.23.24 == 3.23.25 == 3.23.26 == 3.23.27 == 3.23.28-gamma == 3.23.28 == 3.23.29 == 3.23.30 == 3.23.31 == 3.23.34 == 3.23.36 == 3.23.37 == 3.23.38 == 3.23.39 == 3.23.40 == 3.23.41 == 3.23.42 == 3.23.43 == 3.23.44 == 3.23.45 == 3.23.46 == 3.23.47 == 3.23.48 == 3.23.49 == 3.23.50 == 3.23.51 == 3.23.52
CVE-2002-1923	High	December 31, 2002 12/31/02	== 3.20.32a == 3.22.26 == 3.22.27 == 3.22.28 == 3.22.29 == 3.22.30 == 3.22.32 == 3.23.2 == 3.23.3 == 3.23.4 == 3.23.5 == 3.23.8 == 3.23.9 == 3.23.10 == 3.23.23 == 3.23.24 == 3.23.25 == 3.23.26 == 3.23.27 == 3.23.28-gamma == 3.23.28 == 3.23.29 == 3.23.30 == 3.23.31 == 3.23.34 == 3.23.36 == 3.23.37 == 3.23.38 == 3.23.39 == 3.23.40 == 3.23.41 == 3.23.42 == 3.23.43 == 3.23.44 == 3.23.45 == 3.23.46 == 3.23.47 == 3.23.48 == 3.23.49 == 3.23.50 == 3.23.51 == 3.23.52
CVE-2002-1373	Medium	December 23, 2002 12/23/02	== 3.22.26 == 3.22.27 == 3.22.28 == 3.22.29 == 3.22.30 == 3.22.32 == 3.23.2 == 3.23.3 == 3.23.4 == 3.23.5 == 3.23.8 == 3.23.9 == 3.23.10 == 3.23.23 == 3.23.24 == 3.23.25 == 3.23.26 == 3.23.27 == 3.23.28 == 3.23.29 == 3.23.30 == 3.23.31 == 3.23.34 == 3.23.36 == 3.23.37 == 3.23.38 == 3.23.39 == 3.23.40 == 3.23.41 == 3.23.42 == 3.23.43 == 3.23.44 == 3.23.45 == 3.23.46 == 3.23.47 == 3.23.48 == 3.23.49 == 3.23.50 == 3.23.51 == 3.23.52 == 3.23.53 == 3.23.53a == 4.0.0 == 4.0.1 == 4.0.2 == 4.0.3 == 4.0.5a
CVE-2002-1374	High	December 23, 2002 12/23/02	== 3.22.26 == 3.22.27 == 3.22.28 == 3.22.29 == 3.22.30 == 3.22.32 == 3.23.2 == 3.23.3 == 3.23.4 == 3.23.5 == 3.23.8 == 3.23.9 == 3.23.10 == 3.23.23 == 3.23.24 == 3.23.25 == 3.23.26 == 3.23.27 == 3.23.28 == 3.23.29 == 3.23.30 == 3.23.31 == 3.23.34 == 3.23.36 == 3.23.37 == 3.23.38 == 3.23.39 == 3.23.40 == 3.23.41 == 3.23.42 == 3.23.43 == 3.23.44 == 3.23.45 == 3.23.46 == 3.23.47 == 3.23.48 == 3.23.49 == 3.23.50 == 3.23.51 == 3.23.52 == 3.23.53 == 3.23.53a == 4.0.0 == 4.0.1 == 4.0.2 == 4.0.3 == 4.0.5a
CVE-2002-1375	High	December 23, 2002 12/23/02	== 3.22.26 == 3.22.27 == 3.22.28 == 3.22.29 == 3.22.30 == 3.22.32 == 3.23.2 == 3.23.3 == 3.23.4 == 3.23.5 == 3.23.8 == 3.23.9 == 3.23.10 == 3.23.23 == 3.23.24 == 3.23.25 == 3.23.26 == 3.23.27 == 3.23.28 == 3.23.29 == 3.23.30 == 3.23.31 == 3.23.34 == 3.23.36 == 3.23.37 == 3.23.38 == 3.23.39 == 3.23.40 == 3.23.41 == 3.23.42 == 3.23.43 == 3.23.44 == 3.23.45 == 3.23.46 == 3.23.47 == 3.23.48 == 3.23.49 == 3.23.50 == 3.23.51 == 3.23.52 == 3.23.53 == 3.23.53a == 4.0.0 == 4.0.1 == 4.0.2 == 4.0.3 == 4.0.5a
CVE-2002-1376	High	December 23, 2002 12/23/02	== 3.22.26 == 3.22.27 == 3.22.28 == 3.22.29 == 3.22.30 == 3.22.32 == 3.23.2 == 3.23.3 == 3.23.4 == 3.23.5 == 3.23.8 == 3.23.9 == 3.23.10 == 3.23.23 == 3.23.24 == 3.23.25 == 3.23.26 == 3.23.27 == 3.23.28 == 3.23.29 == 3.23.30 == 3.23.31 == 3.23.34 == 3.23.36 == 3.23.37 == 3.23.38 == 3.23.39 == 3.23.40 == 3.23.41 == 3.23.42 == 3.23.43 == 3.23.44 == 3.23.45 == 3.23.46 == 3.23.47 == 3.23.48 == 3.23.49 == 3.23.50 == 3.23.51 == 3.23.52 == 3.23.53 == 3.23.53a == 4.0.0 == 4.0.1 == 4.0.2 == 4.0.3 == 4.0.5a
CVE-2002-0969	High	October 11, 2002 10/11/02	< 3.23.50 >= 4.0.0 <= 4.0.2
CVE-2001-1255	Low	October 2, 2001 10/2/01	== 3.23
CVE-2001-0407	Low	June 27, 2001 6/27/01	<= 3.23.36
CVE-2001-1453	High	February 9, 2001 2/9/01	== 3.23.32
CVE-2001-1454	High	February 9, 2001 2/9/01	<= 3.23.32
CVE-2001-1274	High	January 23, 2001 1/23/01	<= 3.23.31
CVE-2001-1275	High	January 19, 2001 1/19/01	<= 3.23.31
CVE-2000-0981	High	December 19, 2000 12/19/00	== 3.20 == 3.21 == 3.22 == 3.23
CVE-2000-0148	High	February 8, 2000 2/8/00	== 3.22.26 == 3.22.27 == 3.22.29 == 3.22.30 == 3.23.8 == 3.23.9 == 3.23.10
CVE-2000-0045	Medium	January 11, 2000 1/11/00	== 3.22.27 == 3.22.29 == 3.23.8
CVE-1999-1188	Low	December 27, 1998 12/27/98	== 3.21

Showing vulnerabilities for 6 products matching "mysql". Each product has independent pagination.

Deep Security Visibility Without the Complexity

SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.

No setup fees
5-min deployment
Cancel anytime

Book a Demo

Frequently Asked Questions

What is a Vulnerability (CVE) and why does it matter?

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.