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

Found 1 matching product.

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

sgi / irix

29 vulnerabilities found (with exploits)

Title	Severity	Date	Affected Version
CVE-2007-4938	High	September 18, 2007 9/18/07	*
CVE-2005-0465	Low	May 2, 2005 5/2/05	== 6.5.9f == 6.5.16m == 6.5.6 == 6.0.1 == 5.3 == 6.5.4m == 4.0.5_iop == 6.5.17f == 6.5.3f == 4.0 == 3.3.2 == 4.0.5h == 6.5.1 == 6.5.14f == 4.0.4 == 6.5.4f == 4.0.1 == 6.5.10 == 6.5.17 == 6.1 == 6.5.13m == 3.3.1 == 6.5.9m == 6.5.12 == 6.5.10m == 5.0.1 == 4.0.5e == 6.5.15f == 4.0.3 == 6.5.18f == 5.1.1 == 6.5.19f == 6.5.21 == 6.5.21f == 4.0.5a == 6.5.7m == 3.3.3 == 6.5.9 == 6.4 == 6.5.21m == 6.5.19 == 6.5.16f == 6.5.13f == 6.5.20 == 6.5.17m == 4.0.5_ipr == 6.5.20m == 6.5.2f == 5.0 == 6.5.2m == 6.5.15 == 6.5.8m == 6.5.12f == 6.5.6f == 4.0.1t == 6.5.7f == 6.5.14m == 6.5.3 == 5.1 == 6.5.14 == 4.0.5f == 6.5.3m == 6.5.8 == 4.0.5b == 6.5.19m == 6.5.20f == 6.5.5 == 4.0.5g == 5.2 == 6.5.4 == 6.5.15m == 6.5.11f == 6.5_20 == 6.5.11 == 6.0 == 6.5.11m == 6.3 == 6.5.6m == 4.0.5 == 3.3 == 4.0.4b == 6.5.2 == 6.5.8f == 6.5.5f == 6.5 == 6.5.7 == 6.5.18 == 6.5.18m == 6.5.22 == 6.2 == 4.0.2 == 4.0.4t == 6.5.10f == 6.5.5m == 6.5.13 == 6.5.12m == 6.5.16 == 3.2
CVE-2002-1419	High	April 11, 2003 4/11/03	== 6.5.15 == 6.5.14 == 6.5.13 == 6.5.16
CVE-2003-0028	High	March 25, 2003 3/25/03	== 6.5 == 6.5.1 == 6.5.10 == 6.5.10f == 6.5.10m == 6.5.11 == 6.5.11f == 6.5.11m == 6.5.12 == 6.5.12f == 6.5.12m == 6.5.13 == 6.5.13f == 6.5.13m == 6.5.14 == 6.5.14f == 6.5.14m == 6.5.15 == 6.5.15f == 6.5.15m == 6.5.16 == 6.5.16f == 6.5.16m == 6.5.17 == 6.5.17f == 6.5.17m == 6.5.18 == 6.5.18f == 6.5.18m == 6.5.19 == 6.5.2 == 6.5.20 == 6.5.2f == 6.5.2m == 6.5.3 == 6.5.3f == 6.5.3m == 6.5.4 == 6.5.4f == 6.5.4m == 6.5.5 == 6.5.5f == 6.5.5m == 6.5.6 == 6.5.6f == 6.5.6m == 6.5.7 == 6.5.7f == 6.5.7m == 6.5.8 == 6.5.8f == 6.5.8m == 6.5.9 == 6.5.9f == 6.5.9m
CVE-2002-2185	Low	December 31, 2002 12/31/02	== 6.5 == 6.5.1 == 6.5.10 == 6.5.11 == 6.5.12 == 6.5.13 == 6.5.14f == 6.5.14m == 6.5.15f == 6.5.15m == 6.5.16f == 6.5.16m == 6.5.17f == 6.5.17m == 6.5.18f == 6.5.18m == 6.5.2 == 6.5.3 == 6.5.4 == 6.5.5 == 6.5.6 == 6.5.7 == 6.5.8 == 6.5.9
CVE-2001-0797	High	December 12, 2001 12/12/01	== 3.3.2 == 3.3.1 == 3.3.3 == 3.3 == 3.2
CVE-2001-0799	High	December 6, 2001 12/6/01	<= 6.5.13f
CVE-2001-0801	High	December 6, 2001 12/6/01	<= 6.5.13f
CVE-2001-0554	High	August 14, 2001 8/14/01	== 6.5
CVE-2001-0485	High	June 27, 2001 6/27/01	== 6.2
CVE-2001-0247	High	June 18, 2001 6/18/01	== 6.5.6 == 6.5.3f == 6.5.1 == 6.5.10 == 6.1 == 6.5.2m == 6.5.3 == 6.5.3m == 6.5.8 == 6.5.5 == 6.5.4 == 6.5.11 == 6.5.7
CVE-2001-0248	Critical	June 18, 2001 6/18/01	== 6.5 == 6.5.1 == 6.5.2
CVE-2000-0844	High	November 14, 2000 11/14/00	== 6.5.6 == 6.5.3f == 6.5.1 == 6.4 == 6.5.2m == 6.5.3 == 6.5.3m == 6.5.8 == 6.5.4 == 6.3 == 6.5 == 6.5.7 == 6.2
CVE-2000-0733	High	October 20, 2000 10/20/00	== 6.5.6 == 6.0.1 == 5.3 == 6.5.3f == 6.5.1 == 6.1 == 6.4 == 6.5.2m == 6.5.3 == 6.5.3m == 6.5.8 == 5.2 == 6.5.4 == 6.0 == 6.3 == 6.5 == 6.5.7 == 6.2
CVE-2000-0579	Low	June 21, 2000 6/21/00	== 6.3 == 6.5
CVE-2000-0283	Medium	April 12, 2000 4/12/00	== 6.5.6 == 6.5.3f == 6.4 == 6.5.3 == 6.5.3m == 6.5.4 == 6.3 == 6.2
CVE-1999-1102	Low	December 31, 1999 12/31/99	<= 5.2
CVE-1999-1409	Low	July 3, 1998 7/3/98	== 6.5.1 == 6.4 == 6.5 == 6.2
CVE-1999-1114	High	April 8, 1998 4/8/98	== 6.0.1 == 5.3 == 6.1 == 5.0.1 == 5.1.1 == 6.4 == 5.0 == 5.1 == 5.2 == 6.0 == 6.3 == 6.2
CVE-1999-0018	High	December 5, 1997 12/5/97	== 5.3 == 5.0.1 == 5.1.1 == 5.0 == 5.1 == 5.2
CVE-1999-1399	High	August 20, 1997 8/20/97	== 6.2
CVE-1999-1410	Medium	May 9, 1997 5/9/97	== 6.0.1 == 5.3 == 6.1 == 5.0.1 == 5.1.1 == 5.0 == 5.1 == 5.2 == 6.2
CVE-1999-1398	Medium	May 7, 1997 5/7/97	== 6.0.1 == 5.3 == 6.1 == 5.0.1 == 5.1.1 == 6.4 == 5.0 == 5.1 == 5.2 == 6.0 == 6.3 == 6.2
CVE-1999-1461	High	May 7, 1997 5/7/97	== 5.3 == 6.5.10 == 6.1 == 6.4 == 6.3 == 6.2
CVE-1999-1120	Low	January 4, 1997 1/4/97	== 5.3 == 6.0.1 == 6.1 <= 6.4 == 6.0 == 6.3 == 6.2
CVE-1999-1384	High	October 30, 1996 10/30/96	== 6.0.1 == 5.3 <= 6.3 == 6.1 == 5.0.1 == 5.1.1 == 5.0 == 5 == 5.1 == 5.2 == 6.0 == 6.2
CVE-1999-1022	Medium	October 2, 1994 10/2/94	== 5.3 == 5.2 == 4
CVE-1999-1219	High	August 11, 1994 8/11/94	== 5.1 == 5.2
CVE-1999-1494	Low	August 9, 1994 8/9/94	== 6.0.1 == 5.1.1 == 5.1 == 5.2 == 6.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.