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 "java"

Found 5 matching products. Filters apply to all results.

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

sun / java

14 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2010-0887	High	April 20, 2010 4/20/10	== 6-19 == 6-18
CVE-2009-1102	Medium	March 25, 2009 3/25/09	*
CVE-2009-1103	Medium	March 25, 2009 3/25/09	*
CVE-2009-1104	Medium	March 25, 2009 3/25/09	*
CVE-2009-1105	High	March 25, 2009 3/25/09	*
CVE-2009-1107	Low	March 25, 2009 3/25/09	*
CVE-2008-3440	High	August 1, 2008 8/1/08	== 1.6.0 <= 1.6.0 == 1.6.0-02 == 1.6.0-01
CVE-2005-2527	Low	December 31, 2005 12/31/05	<= 1.4.2_release1
CVE-2005-2529	High	December 31, 2005 12/31/05	== 1.4.2
CVE-2005-2530	High	December 31, 2005 12/31/05	== 1.3.1
CVE-2005-2738	Medium	December 31, 2005 12/31/05	== 1.4.2
CVE-2003-1134	Low	December 31, 2003 12/31/03	== 1.4.2 == 1.4.1 == 1.3.1
CVE-1999-0440	High	March 1, 1999 3/1/99	*
CVE-1999-0142	High	March 1, 1996 3/1/96	*

symantec / java

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2002-2281	High		December 31, 2002 12/31/02	== 4.75 == 4.08 == 4.72 == 4.06 == 4.78 == 4.5 == 4.07 == 4.61 == 4.77 == 4.7 == 4.0 == 4.74 == 4.6 == 4.4 == 4.51 == 4.76 == 4.73 == 4.79

apple / java

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2010-0538	Medium		May 21, 2010 5/21/10	*

ibm / java

27 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2023-30441	High	April 29, 2023 4/29/23	>= 8.0.7.0 < 8.0.7.15
CVE-2019-4473	High	August 5, 2019 8/5/19	== 7.0.0.0 == 8.0 == 7.1.4.50
CVE-2015-1916	Medium	July 2, 2015 7/2/15	== 8.0
CVE-2015-1914	Medium	July 2, 2015 7/2/15	>= 5.0.0.0 < 5.0.16.10 >= 6.1.0.0 < 6.1.8.4 >= 6.0.0.0 < 6.0.16.4 >= 7.1.0.0 < 7.1.3.0 >= 7.0.0.0 < 7.0.9.0
CVE-2015-0192	High	July 2, 2015 7/2/15	>= 5.0.0.0 < 5.0.16.10 >= 6.0.0.0 <= 6.0.16.4 >= 6.1.0.0 < 6.1.8.4 >= 7.0.0.0 <= 7.0.9 >= 7.1.0.0 < 7.1.2.11 >= 8.0 < 8.0.1.0
CVE-2014-3068	Medium	December 2, 2014 12/2/14	== 7.0.0.0 == 6.0.3.0 == 6.0.9.0 == 6.0.13.0 == 7.0.2.0 == 6.0.10.1 == 7.0.4.2 == 5.0.12.2 == 6.0.10.0 == 7.0.1.0 == 5.0.12.3 == 5.0.16.3 == 5.0.0.0 == 6.0.13.2 == 5.0.14.0 == 5.0.11.0 == 7.0.4.1 == 6.0.6.0 == 5.0.16.0 == 5.0.12.1 == 6.0.1.0 == 6.0.9.1 == 6.0.12.0 == 6.0.8.1 == 5.0.13.0 == 5.0.16.2 == 5.0.12.4 == 6.0.11.0 == 6.0.5.0 == 6.0.7.0 == 6.0.2.0 == 6.0.13.1 == 7.0.5.0 == 5.0.11.2 == 5.0.11.1 == 6.0.14.0 == 5.0.16.1 == 5.0.12.0 == 5.0.12.5 == 6.0.4.0 == 6.0.9.2 == 6.0.8.0 == 6.0.0.0 == 7.0.3.0 == 7.0.4.0 == 5.0.15.0
CVE-2014-3065	Medium	December 2, 2014 12/2/14	== 7.0.0.0 == 6.0.3.0 == 6.0.9.0 == 6.0.13.0 == 7.0.2.0 == 6.0.10.1 == 7.0.4.2 == 5.0.12.2 == 6.0.10.0 == 7.0.1.0 == 5.0.12.3 == 5.0.16.3 == 5.0.0.0 == 6.0.13.2 == 5.0.14.0 == 5.0.11.0 == 7.0.4.1 == 6.0.6.0 == 5.0.16.0 == 5.0.12.1 == 6.0.1.0 == 6.0.9.1 == 6.0.12.0 == 6.0.8.1 == 5.0.13.0 == 5.0.16.2 == 5.0.12.4 == 6.0.11.0 == 6.0.5.0 == 6.0.7.0 == 6.0.2.0 == 6.0.13.1 == 7.0.5.0 == 5.0.11.2 == 5.0.11.1 == 6.0.14.0 == 5.0.16.1 == 5.0.12.0 == 5.0.12.5 == 6.0.4.0 == 6.0.9.2 == 6.0.8.0 == 6.0.0.0 == 7.0.3.0 == 7.0.4.0 == 5.0.15.0
CVE-2013-0485	High	January 21, 2014 1/21/14	== 7.0.0.0 == 1.4.2 == 5.0.0.0 == 6.0.0.0
CVE-2013-4041	Medium	November 24, 2013 11/24/13	== 7.0.0.0 == 5.0.0.0 == 6.0.1.0 == 6.0.0.0
CVE-2013-5375	Medium	November 24, 2013 11/24/13	== 7.0.0.0 == 5.0.0.0 == 6.0.1.0 == 6.0.0.0
CVE-2013-5456	High	November 24, 2013 11/24/13	== 7.0.0.0
CVE-2013-5457	High	November 24, 2013 11/24/13	== 7.0.0.0 == 6.0.1.0 == 6.0.0.0
CVE-2013-5458	High	November 24, 2013 11/24/13	== 7.0.0.0
CVE-2013-3006	High	July 23, 2013 7/23/13	== 7.0.0.0 == 7.0.2.0 == 7.0.4.2 == 7.0.1.0 == 7.0.4.1 == 7.0.3.0 == 7.0.4.0
CVE-2013-3007	High	July 23, 2013 7/23/13	== 6.0.1.0 == 7.0.0.0 == 7.0.2.0 == 7.0.4.2 == 7.0.1.0 == 7.0.4.1 == 7.0.3.0 == 7.0.4.0
CVE-2013-3008	High	July 23, 2013 7/23/13	== 7.0.0.0 == 7.0.2.0 == 7.0.4.2 == 7.0.1.0 == 7.0.4.1 == 7.0.3.0 == 7.0.4.0
CVE-2013-3009	High	July 23, 2013 7/23/13	== 1.4.2.13.16 == 1.4.2.13.14 == 1.4.2 == 1.4.2.13.5 == 1.4.2.13.13 == 1.4.2.13.4 == 1.4.2.13.11 == 1.4.2.13.9 == 1.4.2.13.15 == 1.4.2.13.2 == 1.4.2.13.7 == 1.4.2.13 == 1.4.2.13.6 == 1.4.2.13.10 == 1.4.2.13.1 == 1.4.2.13.12 == 1.4.2.13.8 == 1.4.2.13.17 == 1.4.2.13.3 == 7.0.0.0 == 7.0.2.0 == 7.0.4.2 == 7.0.1.0 == 7.0.4.1 == 7.0.3.0 == 7.0.4.0 == 6.0.3.0 == 6.0.9.0 == 6.0.13.0 == 6.0.10.1 == 6.0.10.0 == 6.0.13.2 == 6.0.6.0 == 6.0.1.0 == 6.0.9.1 == 6.0.12.0 == 6.0.8.1 == 6.0.11.0 == 6.0.5.0 == 6.0.7.0 == 6.0.2.0 == 6.0.13.1 == 6.0.4.0 == 6.0.9.2 == 6.0.8.0 == 6.0.0.0 == 5.0.12.2 == 5.0.12.3 == 5.0.0.0 == 5.0.14.0 == 5.0.11.0 == 5.0.16.0 == 5.0.12.1 == 5.0.13.0 == 5.0.16.2 == 5.0.12.4 == 5.0.11.2 == 5.0.11.1 == 5.0.16.1 == 5.0.12.0 == 5.0.12.5 == 5.0.15.0
CVE-2013-3010	High	July 23, 2013 7/23/13	== 6.0.1.0 == 7.0.0.0 == 7.0.2.0 == 7.0.4.2 == 7.0.1.0 == 7.0.4.1 == 7.0.3.0 == 7.0.4.0
CVE-2013-3011	High	July 23, 2013 7/23/13	== 5.0.12.2 == 5.0.12.3 == 5.0.0.0 == 5.0.14.0 == 5.0.11.0 == 5.0.16.0 == 5.0.12.1 == 5.0.13.0 == 5.0.16.2 == 5.0.12.4 == 5.0.11.2 == 5.0.11.1 == 5.0.16.1 == 5.0.12.0 == 5.0.12.5 == 5.0.15.0 == 6.0.3.0 == 6.0.9.0 == 6.0.13.0 == 6.0.10.1 == 6.0.10.0 == 6.0.13.2 == 6.0.6.0 == 6.0.1.0 == 6.0.9.1 == 6.0.12.0 == 6.0.8.1 == 6.0.11.0 == 6.0.5.0 == 6.0.7.0 == 6.0.2.0 == 6.0.13.1 == 6.0.4.0 == 6.0.9.2 == 6.0.8.0 == 6.0.0.0 == 7.0.0.0 == 7.0.2.0 == 7.0.4.2 == 7.0.1.0 == 7.0.4.1 == 7.0.3.0 == 7.0.4.0 == 1.4.2.13.16 == 1.4.2.13.14 == 1.4.2 == 1.4.2.13.5 == 1.4.2.13.13 == 1.4.2.13.4 == 1.4.2.13.11 == 1.4.2.13.9 == 1.4.2.13.15 == 1.4.2.13.2 == 1.4.2.13.7 == 1.4.2.13 == 1.4.2.13.6 == 1.4.2.13.10 == 1.4.2.13.1 == 1.4.2.13.12 == 1.4.2.13.8 == 1.4.2.13.17 == 1.4.2.13.3
CVE-2013-3012	High	July 23, 2013 7/23/13	== 5.0.12.2 == 5.0.12.3 == 5.0.0.0 == 5.0.14.0 == 5.0.11.0 == 5.0.16.0 == 5.0.12.1 == 5.0.13.0 == 5.0.16.2 == 5.0.12.4 == 5.0.11.2 == 5.0.11.1 == 5.0.16.1 == 5.0.12.0 == 5.0.12.5 == 5.0.15.0 == 6.0.3.0 == 6.0.9.0 == 6.0.13.0 == 6.0.10.1 == 6.0.10.0 == 6.0.13.2 == 6.0.6.0 == 6.0.1.0 == 6.0.9.1 == 6.0.12.0 == 6.0.8.1 == 6.0.11.0 == 6.0.5.0 == 6.0.7.0 == 6.0.2.0 == 6.0.13.1 == 6.0.4.0 == 6.0.9.2 == 6.0.8.0 == 6.0.0.0 == 7.0.0.0 == 7.0.2.0 == 7.0.4.2 == 7.0.1.0 == 7.0.4.1 == 7.0.3.0 == 7.0.4.0 == 1.4.2.13.16 == 1.4.2.13.14 == 1.4.2 == 1.4.2.13.5 == 1.4.2.13.13 == 1.4.2.13.4 == 1.4.2.13.11 == 1.4.2.13.9 == 1.4.2.13.15 == 1.4.2.13.2 == 1.4.2.13.7 == 1.4.2.13 == 1.4.2.13.6 == 1.4.2.13.10 == 1.4.2.13.1 == 1.4.2.13.12 == 1.4.2.13.8 == 1.4.2.13.17 == 1.4.2.13.3
CVE-2013-4002	High	July 23, 2013 7/23/13	== 5.0.12.2 == 5.0.12.3 == 5.0.0.0 == 5.0.14.0 == 5.0.11.0 == 5.0.16.0 == 5.0.12.1 == 5.0.13.0 == 5.0.16.2 == 5.0.12.4 == 5.0.11.2 == 5.0.11.1 == 5.0.16.1 == 5.0.12.0 == 5.0.12.5 == 5.0.15.0 == 6.0.3.0 == 6.0.9.0 == 6.0.13.0 == 6.0.10.1 == 6.0.10.0 == 6.0.13.2 == 6.0.6.0 == 6.0.1.0 == 6.0.9.1 == 6.0.12.0 == 6.0.8.1 == 6.0.11.0 == 6.0.5.0 == 6.0.7.0 == 6.0.2.0 == 6.0.13.1 == 6.0.4.0 == 6.0.9.2 == 6.0.8.0 == 6.0.0.0 == 7.0.0.0 == 7.0.2.0 == 7.0.4.2 == 7.0.1.0 == 7.0.4.1 == 7.0.3.0 == 7.0.4.0
CVE-2012-4821	High	January 11, 2013 1/11/13	>= 1.4.2 <= 1.4.2.13.13 >= 5.0.0.0 <= 5.0.14.0 >= 6.0.0.0 <= 6.0.11.0 >= 7.0.0.0 <= 7.0.2.0
CVE-2012-4822	High	January 11, 2013 1/11/13	>= 1.4.2 <= 1.4.2.13.13 >= 5.0.0.0 <= 5.0.14.0 >= 6.0.0.0 <= 6.0.11.0 >= 7.0.0.0 <= 7.0.2.0
CVE-2012-4823	High	January 11, 2013 1/11/13	>= 1.4.2 <= 1.4.2.13.13 >= 5.0.0.0 <= 5.0.14.0 >= 6.0.0.0 <= 6.0.11.0 >= 7.0.0.0 <= 7.0.2.0
CVE-2012-4820	High	January 11, 2013 1/11/13	>= 1.4.2 <= 1.4.2.13.13 >= 5.0.0.0 <= 5.0.14.0 >= 6.0.0.0 <= 6.0.11.0 >= 7.0.0.0 <= 7.0.2.0
CVE-2011-3387	Low	September 2, 2011 9/2/11	== 1.4.2.13.9
CVE-2011-0311	Low	September 2, 2011 9/2/11	== 1.4.2 == 1.4.2.13.5 == 1.4.2.13.4 == 1.4.2.13.2 == 1.4.2.13.7 == 1.4.2.13 <= 1.4.2.13.8 == 1.4.2.13.6 == 1.4.2.13.1 == 1.4.2.13.3

kubernetes / java

2 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2021-25738	Medium		October 11, 2021 10/11/21	>= 10.0.0 <= 10.0.1 <= 9.0.2 >= 11.0.0 < 11.0.1
CVE-2020-8570	Critical		January 21, 2021 1/21/21	< 9.0.2 >= 10.0.0 < 10.0.1

Showing vulnerabilities for 5 products matching "java". 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.