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 "hp--ux"

Found 1 matching product.

You can search for specific versions with /product/hp--ux/1.2.3

hp / hp-ux

966 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2000-0573	High	July 7, 2000 7/7/00	== 11.00
CVE-2000-0515	High	June 7, 2000 6/7/00	== 11.00 == 10.20
CVE-2000-0468	Low	June 2, 2000 6/2/00	== 11.00 == 10.20
CVE-2000-0414	Low	May 4, 2000 5/4/00	== 11.00 == 10.20 == 10.10
CVE-2000-0083	Low	April 18, 2000 4/18/00	== 11 == 10
CVE-2000-0251	Medium	April 6, 2000 4/6/00	== 11.4
CVE-1999-0693	High	March 2, 2000 3/2/00	== 11 == 10
CVE-2000-0159	High	February 17, 2000 2/17/00	== 11.00
CVE-2000-0095	Medium	January 24, 2000 1/24/00	== 10.30 == 11.00
CVE-2000-0077	High	January 2, 2000 1/2/00	== 11 == 10
CVE-2000-0078	High	January 2, 2000 1/2/00	== 11 == 10
CVE-1999-1573	High	December 28, 1999 12/28/99	== 10.30 == 10.01 == 10.00 == 11.00 == 10.20 == 10.10
CVE-1999-0688	Low	July 1, 1999 7/1/99	== 11.00 == 10.24
CVE-1999-0690	High	July 1, 1999 7/1/99	== 10
CVE-1999-0696	High	July 1, 1999 7/1/99	== 11.00 == 10.24
CVE-1999-0707	High	July 1, 1999 7/1/99	== 10.20
CVE-1999-0686	Medium	May 7, 1999 5/7/99	== 10.24
CVE-1999-0432	Low	March 1, 1999 3/1/99	== 11.00
CVE-1999-0435	High	March 1, 1999 3/1/99	== 10.01 == 10.00 == 11.00 == 10.20
CVE-1999-0436	Low	March 1, 1999 3/1/99	== 11.00 == 10.20
CVE-1999-0479	Medium	March 1, 1999 3/1/99	== 10.24
CVE-1999-1247	High	February 24, 1999 2/24/99	== 9
CVE-1999-0353	High	February 10, 1999 2/10/99	== 10.01 == 11.00 == 10.20 == 10.10
CVE-2000-0005	High	January 2, 1999 1/2/99	== 9.08 == 10.30 == 9.06 == 9.04 == 9.10 == 10.01 == 7.04 == 10.00 == 9.03 == 8.08 == 8.04 == 10.34 == 11.00 == 8.09 == 8.01 == 7.00 == 10.24 == 8.07 == 9.00 == 9.09 == 7.06 == 8.00 == 10.08 == 9.05 == 8.06 == 10.20 == 8.05 == 9.07 == 9.01 == 8.02 == 7.08 == 10.09 == 7.02 == 10.10 == 10.16
CVE-1999-0057	High	November 16, 1998 11/16/98	== 10.00 == 9 == 10.24 == 10.09
CVE-1999-0779	Medium	September 3, 1998 9/3/98	== 10.01 == 11.00 == 10.20 == 10.10
CVE-1999-0333	High	August 1, 1998 8/1/98	*
CVE-1999-1136	Low	July 30, 1998 7/30/98	<= 11.00
CVE-1999-0008	High	June 8, 1998 6/8/98	== 10.34 == 11.00
CVE-1999-0003	High	April 1, 1998 4/1/98	== 10.02 == 10.01 == 11.00 == 10.03
CVE-1999-0502	High	March 1, 1998 3/1/98	== 11 == 10.20
CVE-1999-0014	High	January 21, 1998 1/21/98	== 11.00 == 10.20 == 10.10
CVE-1999-0513	Medium	January 5, 1998 1/5/98	== 11.00 == 10.20
CVE-1999-0015	Medium	December 16, 1997 12/16/97	== 10.30 == 9.04 == 10.01 == 9.03 == 11.00 == 10.24 == 10 == 9.00 == 9.05 == 10.20 == 9.07 == 9.01 == 10.16
CVE-1999-0104	Medium	December 16, 1997 12/16/97	*
CVE-1999-0016	Medium	December 1, 1997 12/1/97	== 10.30 == 9.04 == 10.01 == 10.00 == 9.03 == 11.00 == 10.24 == 9.00 == 9.05 == 10.20 == 9.07 == 9.01 == 10.10 == 10.16
CVE-1999-0216	Medium	November 1, 1997 11/1/97	== 10
CVE-1999-0097	High	October 29, 1997 10/29/97	== 9.08 == 9.06 == 9.04 == 9.10 == 10.00 == 9.03 == 11.00 == 10.24 == 9.00 == 9.09 == 9.05 == 10.20 == 9.07 == 9.01 == 10.10 == 10.16
CVE-1999-0326	Low	October 1, 1997 10/1/97	== 10.30 == 10.01 == 9 == 10.20 == 10.10
CVE-1999-1213	Medium	October 1, 1997 10/1/97	== 10.30
CVE-1999-1133	Low	September 1, 1997 9/1/97	== 9 == 10
CVE-1999-1139	High	September 1, 1997 9/1/97	<= 11.00
CVE-1999-1308	Low	July 31, 1997 7/31/97	== 10.20
CVE-1999-0962	High	May 14, 1997 5/14/97	== 9 == 10
CVE-1999-0040	High	May 1, 1997 5/1/97	== 10.30 == 9.10 == 10.01 == 10.00 == 10.34 == 10.24 == 9.00 == 10.08 == 10.20 == 9.01 == 10.09 == 10.10 == 10.16
CVE-1999-0038	High	April 26, 1997 4/26/97	== 10.30 == 10.01 == 10.00 == 10.34 == 10.24 == 10.08 == 10.20 == 10.10 == 10.16
CVE-1999-1408	Low	March 5, 1997 3/5/97	== 10.01 == 9.05 == 10.20
CVE-1999-0318	High	March 1, 1997 3/1/97	== 11
CVE-1999-0046	High	February 6, 1997 2/6/97	== 10.30 == 10.01 == 10.00 == 10.34 == 10.24 == 10.08 == 10.20 == 10.09 == 10.10 == 10.16
CVE-1999-1160	High	February 2, 1997 2/2/97	== 9 == 10

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.