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.

346,508

Total vulnerabilities in the database

Vulnerabilities for products matching "netware"

Found 2 matching products. Filters apply to all results.

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

novell / netware

219 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2011-4191	High	November 30, 2011 11/30/11	== 6.5-sp8
CVE-2010-4228	High	March 22, 2011 3/22/11	== 5.1 == 6.0 == 6.5
CVE-2010-4227	High	February 25, 2011 2/25/11	== 6.5 == 6.5-sp1 == 6.5-sp4 <= 6.5 == 6.5-sp2 == 6.5-sp6 == 6.5-sp3 == 6.5-sp5
CVE-2010-2351	High	June 21, 2010 6/21/10	== 6.5 == 6.0-sp1 == 6.5-sp1 == 5.1 == 6.5-sp4 == 6.0-sp3 == 5.0-sp3 == 6.0-sp4 == 6.5-sp2 == 6.5-sp6 == 6.0 == 6.0-sp5 == 6.5-sp3 == 6.5-sp7 == 6.5-sp5 == 5.1-sp8 == 5.0 == 5.1-sp7 == 6.0-sp2 <= 6.5
CVE-2010-0625	Medium	April 5, 2010 4/5/10	== 5.1-sp6 == 5.1 == 5.1-sp4 == 5.1-sp3 == 5.1-sp2a == 6.0-sp1 == 6.0-sp2 == 6.0 == 6.0-sp3 == 6.5-sp2 == 6.5-sp1 == 6.5-sp6 == 6.5-sp3 == 6.5-sp1.1a == 6.5-sp4 == 6.5-sp8 == 6.5-sp1.1b == 6.5-sp5 == 6.5-sp7 == 6.5
CVE-2000-1245	High	April 5, 2010 4/5/10	== 5.1-sp3
CVE-2000-1246	Low	April 5, 2010 4/5/10	== 5.1-sp3
CVE-2001-1587	Medium	April 5, 2010 4/5/10	*
CVE-2002-2432	Medium	April 5, 2010 4/5/10	*
CVE-2002-2433	Low	April 5, 2010 4/5/10	== 5.1 == 6.0 == 6.5
CVE-2002-2434	Medium	April 5, 2010 4/5/10	== 5.1 == 6.0 == 6.5
CVE-2003-1591	Low	April 5, 2010 4/5/10	== 6.0-sp3 == 6.0-sp1 == 6.0 == 6.0-sp2 == 6.5
CVE-2003-1592	Medium	April 5, 2010 4/5/10	== 6.0-sp3 == 6.0-sp1 == 6.0 == 6.0-sp2 == 6.5
CVE-2003-1593	High	April 5, 2010 4/5/10	== 6.0-sp3 == 6.0-sp1 == 6.0 == 6.0-sp2 == 6.5
CVE-2003-1594	High	April 5, 2010 4/5/10	== 6.5
CVE-2003-1595	High	April 5, 2010 4/5/10	== 6.5
CVE-2003-1596	High	April 5, 2010 4/5/10	== 5.1 == 6.0 == 6.5
CVE-2004-2767	Low	April 5, 2010 4/5/10	*
CVE-2005-4887	High	April 5, 2010 4/5/10	== 6.5-sp5
CVE-2005-4888	Medium	April 5, 2010 4/5/10	*
CVE-2007-6734	Low	April 5, 2010 4/5/10	== 6.5-sp7
CVE-2007-6735	High	April 5, 2010 4/5/10	*
CVE-2010-0317	High	January 15, 2010 1/15/10	== 6.5-sp8
CVE-2008-5696	High	December 19, 2008 12/19/08	== 6.5-sp6 <= 6.5 == 6.5-sp3 == 6.5-sp1 == 6.5-sp2 == 6.5-sp1.1a == 6.5-sp4 == 6.5-sp1.1b == 6.5-sp5 == 6.5
CVE-2006-6675	Medium	December 21, 2006 12/21/06	== 6.5-sp6 == 6.5-sp5
CVE-2006-2185	Low	May 22, 2006 5/22/06	== 6.5-sp5
CVE-2006-2327	Medium	May 12, 2006 5/12/06	== 6.5-sp3 == 6.5-sp1 == 6.5-sp2 == 6.5-sp1.1a == 6.5-sp4 == 6.5-sp1.1b == 6.5-sp5 == 6.5
CVE-2006-0997	Medium	March 23, 2006 3/23/06	== 6.5-sp3 == 6.5-sp1 == 6.5-sp2 == 6.5-sp1.1a == 6.5-sp4 == 6.5-sp1.1b == 6.5
CVE-2006-0998	Medium	March 23, 2006 3/23/06	== 6.5-sp3 == 6.5-sp1 == 6.5-sp2 == 6.5-sp1.1a == 6.5-sp4 == 6.5-sp1.1b == 6.5
CVE-2006-0999	Medium	March 23, 2006 3/23/06	== 6.5-sp3 == 6.5-sp1 == 6.5-sp2 == 6.5-sp1.1a == 6.5-sp4 == 6.5-sp1.1b == 6.5
CVE-2006-1322	Medium	March 20, 2006 3/20/06	== 6.5-sp4
CVE-2005-2852	Medium	September 8, 2005 9/8/05	== 6.5-sp3 == 5.1 == 6.5-sp2 == 6.0
CVE-2005-0819	Medium	May 2, 2005 5/2/05	== 6.5-sp3 == 6.5-sp2
CVE-2005-1060	Medium	May 2, 2005 5/2/05	== 6.5-sp3 == 6.5-sp1 == 6.0-sp3 == 6.5-sp2 == 6.0-sp1 == 6.0 == 6.5-sp1.1a == 6.5-sp1.1b == 6.0-sp2 == 6.5
CVE-2004-2103	Low	December 31, 2004 12/31/04	== 5.1 == 6.0
CVE-2004-2104	Medium	December 31, 2004 12/31/04	== 5.1 == 6.0
CVE-2004-2105	Medium	December 31, 2004 12/31/04	== 5.1 == 6.0
CVE-2004-2106	Medium	December 31, 2004 12/31/04	== 5.1 == 6.0
CVE-2004-2414	Low	December 31, 2004 12/31/04	== 6.5-sp1.1a
CVE-2004-2734	High	December 31, 2004 12/31/04	== 6.5-sp1 == 6.5-sp1.1a == 6.5-sp1.1b == 6.5
CVE-2003-0976	High	December 15, 2003 12/15/03	== 6.5-sp1 == 6.5
CVE-2003-1150	High	October 27, 2003 10/27/03	== 6.0-sp3
CVE-2003-0562	Medium	August 27, 2003 8/27/03	== 5.1-sp6 == 5.1 == 5.1-sp4 == 6.0-sp1 == 6.0 == 6.0-sp2
CVE-2002-1413	High	April 11, 2003 4/11/03	== 6.0-sp2
CVE-2002-1417	Medium	April 11, 2003 4/11/03	== 5.1 == 6.0
CVE-2002-1418	Medium	April 11, 2003 4/11/03	== 5.1 == 6.0
CVE-2002-1436	High	April 11, 2003 4/11/03	== 5.1 == 5.1-sp4 == 6.0-sp1 == 6.0
CVE-2002-1437	Medium	April 11, 2003 4/11/03	== 5.1 == 5.1-sp4 == 6.0-sp1 == 6.0
CVE-2002-1438	Medium	April 11, 2003 4/11/03	== 5.1 == 5.1-sp4 == 6.0-sp1 == 6.0
CVE-2002-1634	Medium	December 31, 2002 12/31/02	== 5.1 == 5.0

microfocus / netware

8 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2009-5153	High		November 21, 2018 11/21/18	== 6.5-sp4 == 6.5-sp5 == 6.5-sp7 == 6.5-sp1 == 6.5-sp2 == 6.5-sp3 == 6.5-sp6 <= 6.5

Showing vulnerabilities for 2 products matching "netware". 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.