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

Found 2 matching products. Filters apply to all results.

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

hp / tru64

31 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2008-4414	High	November 7, 2008 11/7/08	== 5.1b4 == 5.1b3
CVE-2007-6519	Low	December 24, 2007 12/24/07	== 5.1b4 == 5.1b3
CVE-2007-2791	High	May 22, 2007 5/22/07	== 5.1b4 == 5.1b3
CVE-2007-2553	High	May 9, 2007 5/9/07	== 5.1b4 == 5.1b3 == 5.1a-pk6
CVE-2007-0805	Low	February 7, 2007 2/7/07	== 5.1
CVE-2006-6418	High	December 10, 2006 12/10/06	== 4.0f-pk8 == 5.1a-pk6 == 4.0g-pk4
CVE-2006-5452	Low	October 23, 2006 10/23/06	== 4.0g == 5.0a == 5.1af == 4.0f == 5.1a == 4.0f-pk8 == 5.1b3 == 5.1b-pk1 == 5.1a-pk6 == 5.1 == 4.0g-pk4 == 5.1b2-pk4
CVE-2005-3670	High	November 18, 2005 11/18/05	== 5.1b1-pk4 == 5.1b3
CVE-2005-2993	Low	September 20, 2005 9/20/05	== 4.0f-pk8 <= 5.1b3
CVE-2005-0719	Low	March 9, 2005 3/9/05	== 5.1b1-pk4 == 4.0f-pk8 == 5.1b1-pk3 == 5.1a-pk6 == 4.0g-pk4
CVE-2004-2678	Medium	December 31, 2004 12/31/04	== 5.1b_p3k_bl24 == 5.1a-pk6 == 5.1b_pk2_bl22
CVE-2003-1496	High	December 31, 2003 12/31/03	== 5.1a_pk2_bl2 == 4.0g == 4.0f == 5.1a == 4.0g_pk4_bl22 == 4.0f_pk7_bl18 == 5.1a_pk4_bl21 == 5.1a_pk1_bl1 == 5.1a_pk5_bl23 == 4.0f_pk8_bl22 == 5.1_pk5_bl19 == 5.1_pk6_bl20 == 4.0g_pk3_bl17 == 5.1 == 5.1a_pk3_bl3 == 4.0f_pk6_bl17 == 5.1_pk3_bl17 == 5.1_pk4_bl18 == 5.1b
CVE-2003-0221	High	May 12, 2003 5/12/03	<= 5.1b
CVE-2002-1474	Medium	April 22, 2003 4/22/03	== 4.0g == 5.0a == 4.0f
CVE-2002-1475	Medium	April 22, 2003 4/22/03	== 4.0g == 5.0a == 4.0f
CVE-2002-1617	High	December 31, 2002 12/31/02	== 5.1b_pk2_bl22
CVE-2002-1784	Medium	December 31, 2002 12/31/02	== 4.0g == 5.0a == 4.0f == 5.1a == 5.1
CVE-2002-1612	High	September 13, 2002 9/13/02	== 4.0g == 5.0a == 4.0f == 5.1a == 5.1
CVE-2002-1615	High	September 13, 2002 9/13/02	== 4.0g == 5.0a == 4.0f == 5.1a == 5.1
CVE-2002-1613	High	September 10, 2002 9/10/02	== 4.0g == 5.0a == 4.0f == 5.1a == 5.1
CVE-2002-1614	High	September 9, 2002 9/9/02	== 4.0g == 5.0a == 4.0f == 5.1a == 5.1
CVE-2002-1604	High	September 2, 2002 9/2/02	== 4.0g == 5.0a == 4.0f == 5.1a == 5.1
CVE-2002-1605	High	September 2, 2002 9/2/02	== 4.0g == 5.0a == 4.0f == 5.1a == 5.1
CVE-2002-1607	Low	August 31, 2002 8/31/02	== 4.0g == 5.0a == 4.0f == 5.1a == 5.1
CVE-2002-1608	Low	August 31, 2002 8/31/02	== 4.0g == 5.0a == 4.0f == 5.1a == 5.1
CVE-2002-1606	Low	August 30, 2002 8/30/02	== 4.0g == 5.0a == 4.0f == 5.1a == 5.1
CVE-2002-1609	Low	August 30, 2002 8/30/02	== 4.0g == 5.0a == 4.0f == 5.1a == 5.1
CVE-2002-1610	Low	August 30, 2002 8/30/02	== 4.0g == 5.0a == 4.0f == 5.1a == 5.1
CVE-2002-1611	Low	August 30, 2002 8/30/02	== 4.0g == 5.0a == 4.0f == 5.1a == 5.1
CVE-2002-1616	High	August 1, 2002 8/1/02	== 4.0g == 5.0a == 5.1af == 4.0f == 5.1
CVE-2000-1031	Low	December 11, 2000 12/11/00	== 4.0g == 5.0a == 4.0f == 5.1a == 4.0f-pk8 == 5.1 == 4.0g-pk4

compaq / tru64

23 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2005-0223	Medium	May 2, 2005 5/2/05	*
CVE-2003-0914	Low	December 15, 2003 12/15/03	== 5.1_pk3_bl17 == 5.1_pk4_bl18 == 5.1b_pk1_bl1 == 4.0f_pk6_bl17 == 5.1a_pk3_bl3 == 5.1a_pk4_bl21 == 4.0f == 5.1_pk5_bl19 == 4.0g == 4.0g_pk3_bl17 == 4.0f_pk8_bl22 == 5.1_pk6_bl20 == 5.1 == 5.1a_pk5_bl23 == 5.1b == 4.0g_pk4_bl22 == 5.1a_pk1_bl1 == 5.1a_pk2_bl2 == 4.0f_pk7_bl18 == 5.1a == 5.1b_pk2_bl22
CVE-2003-0688	Medium	October 20, 2003 10/20/03	== 5.0a == 5.1
CVE-2003-0724	High	October 20, 2003 10/20/03	== 5.1a_pk4_bl21 == 5.1a_pk3_bl3 == 5.1b_pk2_bl22 == 5.1a == 5.1a_pk5_bl23 == 5.1a_pk2_bl2 == 5.1a_pk1_bl1
CVE-2003-0694	High	October 6, 2003 10/6/03	== 4.0f == 4.0f_pk6_bl17 == 4.0f_pk7_bl18 == 4.0f_pk8_bl22 == 4.0g == 4.0g_pk3_bl17 == 4.0g_pk4_bl22 == 5.1 == 5.1_pk3_bl17 == 5.1_pk4_bl18 == 5.1_pk5_bl19 == 5.1_pk6_bl20 == 5.1a == 5.1a_pk1_bl1 == 5.1a_pk2_bl2 == 5.1a_pk3_bl3 == 5.1a_pk4_bl21 == 5.1a_pk5_bl23 == 5.1b == 5.1b_pk1_bl1 == 5.1b_pk2_bl22
CVE-2003-0196	High	May 5, 2003 5/5/03	== 5.0a_pk3_bl17 == 5.1_pk3_bl17 == 4.0d_pk9_bl17 == 5.1_pk4_bl18 == 4.0d == 5.0_pk4_bl18 == 5.0a == 4.0b == 4.0g_pk3_bl17 == 5.0 == 5.0_pk4_bl17 == 5.1b_pk1_bl1 == 4.0f == 4.0f_pk6_bl17 == 4.0g == 5.1a_pk3_bl3 == 5.1_pk6_bl20 == 5.1a == 5.1_pk5_bl19 == 5.0f == 5.1a_pk1_bl1 == 5.1a_pk2_bl2 == 4.0f_pk7_bl18 == 5.1 == 5.1b
CVE-2003-0201	High	May 5, 2003 5/5/03	== 5.0a_pk3_bl17 == 5.1_pk3_bl17 == 4.0d_pk9_bl17 == 4.0f == 4.0f_pk6_bl17 == 5.0a == 4.0d == 5.0_pk4_bl17 == 5.0_pk4_bl18 == 4.0g == 5.1a_pk3_bl3 == 4.0g_pk3_bl17 == 5.0 == 5.1_pk4_bl18 == 5.1b_pk1_bl1 == 4.0b == 5.1_pk5_bl19 == 5.1_pk6_bl20 == 5.1a == 5.1a_pk1_bl1 == 4.0f_pk7_bl18 == 5.0f == 5.1 == 5.1a_pk2_bl2 == 5.1b
CVE-2003-0161	High	April 2, 2003 4/2/03	== 4.0b == 4.0d == 4.0d_pk9_bl17 == 4.0f == 4.0f_pk6_bl17 == 4.0f_pk7_bl18 == 4.0g == 4.0g_pk3_bl17 == 5.0 == 5.0_pk4_bl17 == 5.0_pk4_bl18 == 5.0a == 5.0a_pk3_bl17 == 5.0f == 5.1 == 5.1_pk3_bl17 == 5.1_pk4_bl18 == 5.1_pk5_bl19 == 5.1_pk6_bl20 == 5.1a == 5.1a_pk1_bl1 == 5.1a_pk2_bl2 == 5.1a_pk3_bl3 == 5.1b == 5.1b_pk1_bl1
CVE-2002-2002	High	December 31, 2002 12/31/02	== 5.0 == 4.0f == 5.1a == 5.1
CVE-2002-2003	Medium	December 31, 2002 12/31/02	== 4.0g == 5.0a == 4.0f == 5.1a == 5.1
CVE-2002-2004	Medium	December 31, 2002 12/31/02	== 4.0g == 5.0a
CVE-2002-2071	Medium	December 31, 2002 12/31/02	== 4.0e
CVE-2002-1202	High	October 28, 2002 10/28/02	== 5.0a_pk3_bl17 == 4.0g_pk3_bl17 == 5.1a_pk3_bl3 == 5.1_pk5_bl19 == 4.0f_pk7_bl18
CVE-2002-1129	High	October 4, 2002 10/4/02	== 5.0a_pk3_bl17 == 5.1_pk3_bl17 == 5.1_pk4_bl18 == 5.0_pk4_bl18 == 5.0_pk4_bl17 == 5.0 == 4.0f_pk6_bl17 == 4.0g == 4.0g_pk3_bl17 == 5.0a == 4.0f == 5.1_pk5_bl19 == 5.1a == 5.1 == 5.1a_pk2_bl2 == 4.0f_pk7_bl18 == 5.1a_pk1_bl1
CVE-2002-0093	High	September 5, 2002 9/5/02	== 4.0g == 5.0a == 4.0f == 5.1a == 5.1
CVE-2002-0679	High	September 5, 2002 9/5/02	== 4.0g == 5.0a == 4.0f == 5.1a == 5.1
CVE-2002-0816	High	August 12, 2002 8/12/02	== 5.0 == 4.0g == 5.0a == 4.0f == 5.1a == 5.1
CVE-2002-0677	High	July 23, 2002 7/23/02	== 4.0g == 5.0a == 4.0f == 5.1a == 5.1
CVE-2002-0678	High	July 23, 2002 7/23/02	== 4.0g == 5.0a == 4.0f == 5.1a == 5.1
CVE-2001-1033	Medium	September 25, 2001 9/25/01	== 5.0 == 5.1
CVE-2001-1092	Low	September 10, 2001 9/10/01	== 4.0d == 4.0g == 4.0f == 4.0e
CVE-2001-1093	High	September 10, 2001 9/10/01	== 4.0d == 4.0g == 4.0f == 4.0e
CVE-2001-1435	Medium	February 23, 2001 2/23/01	== 5.1

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