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,181

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

33 vulnerabilities found (with exploits)

Title	Severity	Date	Affected Version
CVE-2012-1823	Critical	May 11, 2012 5/11/12	== b.11.23 == b.11.31
CVE-2006-5556	Low	October 27, 2006 10/27/06	== 11.11 == 11.4 == 11.00
CVE-2006-5557	Low	October 27, 2006 10/27/06	== 11.11 == 11.4 == 11.00
CVE-2006-5558	High	October 27, 2006 10/27/06	== 11.11 == 11.4 == 11.00 == 11.23
CVE-2005-3670	High	November 18, 2005 11/18/05	== 11.11 == 11.00 == 11.23
CVE-2005-3277	High	October 21, 2005 10/21/05	== 11.11 == 11.00 == 10.20
CVE-2004-0940	High	February 9, 2005 2/9/05	== 11.11 == 11.00 == 11.22 == 11.20
CVE-2004-0809	Medium	September 16, 2004 9/16/04	== 11.11 == 11.00 == 11.23 == 11.22
CVE-2003-1097	High	December 31, 2003 12/31/03	== 10.30 == 11.11 == 10.26 == 11.04 == 10.34 == 11.00 == 10.24 == 11.22 == 10.20 == 10.10 == 10.16 == 11.20
CVE-2003-1358	High	December 31, 2003 12/31/03	== 10.30 == 11.11 == 10.01 == 10.00 == 10.26 == 11.04 == 10.34 == 11.00 == 11.0.4 == 10.16 == 10.20 == 10.09 == 10.10 == 10.24 == 11.20 == 11.22 == 10.08
CVE-2003-1359	High	December 31, 2003 12/31/03	== 10.00 == 10.01 == 10.08 == 10.09 == 10.10 == 10.16 == 10.20 == 10.24 == 10.26 == 10.30 == 10.34 == 11.0.4 == 11.00 == 11.04 == 11.11 == 11.20 == 11.22
CVE-2003-1374	Low	December 31, 2003 12/31/03	== 11
CVE-2003-1375	High	December 31, 2003 12/31/03	== 11.11 == 11.04 == 11.00 == 10.20
CVE-2003-1461	High	December 31, 2003 12/31/03	== 11.00
CVE-2003-0201	High	May 5, 2003 5/5/03	== 11.11 == 10.01 == 11.04 == 11.00 == 10.20 == 10.24 == 11.20 == 11.22
CVE-2002-1409	Low	April 11, 2003 4/11/03	== 11.11 == 11.04 == 11.00
CVE-2003-0028	High	March 25, 2003 3/25/03	== 11.11 == 11.04 == 11.22 == 11.20 == 10.20 == 10.24 == 11.00
CVE-2002-1337	High	March 7, 2003 3/7/03	== 11.11 == 11.00 == 11.0.4 == 11.22 == 10.20 == 10.10
CVE-2002-1604	High	September 2, 2002 9/2/02	== 11.11 == 11.04 == 11.00 == 11.22 == 10.20
CVE-2002-1605	High	September 2, 2002 9/2/02	== 11.11 == 11.04 == 11.00 == 11.22 == 10.20
CVE-2001-0797	High	December 12, 2001 12/12/01	== 11.11 == 10.01 == 10.00 == 11.00 == 11.0.4 == 10.24 == 10.20 == 10.10
CVE-2001-0979	High	September 3, 2001 9/3/01	== 10.01 == 11.00 == 10.20 == 10.10
CVE-2001-1264	High	July 19, 2001 7/19/01	== 11.04
CVE-2001-1181	High	July 16, 2001 7/16/01	== 11.11
CVE-2001-1244	Medium	July 7, 2001 7/7/01	== 11.11 == 11.00 == 11.0.4
CVE-2001-0248	Critical	June 18, 2001 6/18/01	== 11.00
CVE-2000-1127	Low	January 9, 2001 1/9/01	== 10.20
CVE-2000-1134	High	January 9, 2001 1/9/01	== 11.11
CVE-2000-0972	Medium	December 19, 2000 12/19/00	== 11.00
CVE-2000-1028	High	December 11, 2000 12/11/00	== 9.08 == 9.06 == 9.04 == 9.10 == 11.00 == 9.00 == 9.09 == 9.05 == 10.20 == 9.07 == 9.01
CVE-2000-0702	High	October 20, 2000 10/20/00	== 11.00
CVE-2000-0468	Low	June 2, 2000 6/2/00	== 11.00 == 10.20
CVE-1999-1408	Low	March 5, 1997 3/5/97	== 10.01 == 9.05 == 10.20

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.