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.

325,648

Total vulnerabilities in the database

Vulnerabilities for products matching "java_system_web_server"

Found 1 matching product.

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

sun / java_system_web_server

32 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2010-0387	High	January 25, 2010 1/25/10	== 7.0-update_7
CVE-2010-0388	High	January 25, 2010 1/25/10	== 7.0-update_6
CVE-2010-0389	Medium	January 25, 2010 1/25/10	== 7.0-update_6 == 7.0-update_7
CVE-2010-0360	High	January 20, 2010 1/20/10	== 7.0-update_7
CVE-2010-0361	High	January 20, 2010 1/20/10	== 7.0-update_7
CVE-2010-0272	High	January 8, 2010 1/8/10	== 7.0-update_6
CVE-2010-0273	High	January 8, 2010 1/8/10	== 7.0-update_6
CVE-2009-3878	High	November 5, 2009 11/5/09	== 7.0-update_6
CVE-2009-2712	Low	August 7, 2009 8/7/09	== 7.0
CVE-2009-2713	Low	August 7, 2009 8/7/09	== 7.0
CVE-2009-2445	Medium	July 13, 2009 7/13/09	== 7.0-update_5 == 6.1-sp5 == 6.1-sp8 == 6.1-sp7 == 6.1-sp9 == 7.0-update_6 == 6.1-sp11 == 6.1-sp4 == 6.1-sp10 == 6.1 == 6.1-sp6
CVE-2009-1934	Low	June 5, 2009 6/5/09	== 6.1-sp5 == 6.1-sp8 == 6.1-sp7 == 6.1-sp10 == 6.1-sp9 == 6.1-sp6 == 6.1-sp4 == 6.1-sp48
CVE-2008-2518	Low	June 3, 2008 6/3/08	== 6.1-sp1 == 6.1-sp6 == 6.1-sp3 == 7.0-update_1 == 6.1 == 6.1-sp4 == 6.1-sp5 == 7.0 == 6.1-sp8 == 7.0-update_2 == 6.1-sp2 == 6.1-sp7
CVE-2008-2166	Low	May 13, 2008 5/13/08	== 6.1 == 7.0
CVE-2008-2120	Medium	May 9, 2008 5/9/08	<= 6.1 == 7.0
CVE-2007-6569	Low	December 28, 2007 12/28/07	== 6.1 == 7.0
CVE-2007-6570	Low	December 28, 2007 12/28/07	== 6.0-sp9 == 6.1-sp1 == 6.1-sp6 == 6.0-sp1 == 6.0-sp10 == 6.0 == 6.1-sp3 == 6.0-sp4 == 6.0-sp6 == 6.0-sp2 == 6.1 == 6.0-sp7 == 6.1-sp4 == 6.1-sp5 == 7.0 == 6.0-sp8 == 6.0-sp3 == 6.0-sp5 == 6.1-sp2 == 6.1-sp7
CVE-2007-6571	Low	December 28, 2007 12/28/07	== 6.0-sp9 == 6.1-sp1 == 6.1-sp6 == 6.0-sp1 == 6.0-sp10 == 6.0 == 6.1-sp3 == 6.0-sp4 == 6.0-sp6 == 6.0-sp2 == 6.1 == 6.0-sp7 == 6.1-sp4 == 6.1-sp5 == 7.0 == 6.0-sp8 == 6.0-sp3 == 6.0-sp5 == 6.1-sp2 == 6.1-sp7
CVE-2007-6572	Low	December 28, 2007 12/28/07	== 6.0-sp9 == 6.1-sp1 == 6.1-sp6 == 6.0-sp1 == 6.0-sp10 == 6.0 == 6.1-sp3 == 6.0-sp4 == 6.0-sp6 == 6.0-sp2 == 6.1 == 6.0-sp7 == 6.1-sp4 == 6.1-sp5 == 7.0 == 6.0-sp8 == 6.0-sp3 == 6.0-sp5 == 6.1-sp2 == 6.1-sp7
CVE-2007-4164	High	August 7, 2007 8/7/07	== 6.1-sp1 == 6.1-sp6 == 6.1-sp3 == 6.1 == 6.1-sp4 == 6.1-sp5 == 7.0 == 6.1-sp2 == 6.1-sp7
CVE-2007-3715	High	July 11, 2007 7/11/07	== 7.0
CVE-2007-1526	Medium	March 20, 2007 3/20/07	== 6.1
CVE-2007-1488	High	March 16, 2007 3/16/07	== 6.0-sp9 == 6.1-sp1 == 6.1-sp6 == 6.0-sp1 == 6.0-sp10 == 6.0 == 6.1-sp3 == 6.0-sp4 == 6.0-sp6 == 6.0-sp2 == 6.1 == 6.0-sp7 == 6.1-sp4 == 6.1-sp5 == 6.0-sp8 == 6.0-sp3 == 6.0-sp5 == 6.1-sp2
CVE-2006-6276	Medium	December 4, 2006 12/4/06	== 6.0 == 6.1
CVE-2006-5654	Low	November 3, 2006 11/3/06	== 6.0-sp9
CVE-2006-3921	Low	July 28, 2006 7/28/06	== 6.1-sp1 == 6.0 == 6.1-sp3 == 6.1 == 6.1-sp4 == 6.1-sp5 == 6.1-sp2
CVE-2006-2501	Medium	May 20, 2006 5/20/06	== 6.1-sp1 == 6.1-sp3 == 6.1 <= 6.1 == 6.1-sp2
CVE-2005-1889	Medium	June 7, 2005 6/7/05	== 6.1-sp1 <= 6.1
CVE-2005-1150	Medium	May 2, 2005 5/2/05	== 6.0-sp1 == 6.0 == 6.0-sp4 == 6.0-sp6 == 6.0-sp2 == 6.0-sp7 == 6.0-sp3 == 6.0-sp5
CVE-2004-2216	Medium	December 31, 2004 12/31/04	== 6.1-sp1 == 6.0-sp1 == 6.0 == 6.0-sp4 == 6.0-sp6 == 6.0-sp2 == 6.1 == 6.0-sp7 == 6.0-sp3 == 6.0-sp5
CVE-2000-0812	High	November 14, 2000 11/14/00	== 1.1_beta == 1.1.3 == 2.0 == 1.1.2
CVE-2000-0629	High	July 12, 2000 7/12/00	== 1.1.3 == 2.0

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.