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

Found 1 matching product.

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

ibm / aix

1204 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2000-1124	High	January 9, 2001 1/9/01	== 4.3.2 == 4.3 == 4.3.3 == 4.3.1
CVE-2000-1222	High	December 10, 2000 12/10/00	<= 4.2.1.12
CVE-2000-0844	High	November 14, 2000 11/14/00	== 4.3.2 == 4.3 == 4.2.1 == 3.2.5 == 3.2.4 == 4.1.4 == 4.2 == 4.1.5 == 4.0 == 4.1.1 == 4.1.2 == 4.3.1 == 4.1 == 4.1.3 == 3.2
CVE-2000-0873	Low	November 14, 2000 11/14/00	== 4.3.2 == 4.3 == 4.2.1 == 4.2 == 4.3.1
CVE-2000-0466	High	June 20, 2000 6/20/00	== 4.3.2 == 4.3 == 4.3.1
CVE-2000-0441	Medium	May 24, 2000 5/24/00	== 4.3.2 == 4.3 == 4.2.1 == 3.2.5 == 3.2.4 == 4.1.4 == 4.2 == 4.1.5 == 4.1.1 == 4.1.2 == 4.3.1 == 4.1 == 4.1.3 == 3.2
CVE-2000-0249	High	April 26, 2000 4/26/00	== 4.3.2 == 4.3 == 4.3.1
CVE-1999-0693	High	March 2, 2000 3/2/00	== 4
CVE-2000-1216	High	January 27, 2000 1/27/00	== 4.3.0
CVE-2000-0080	Low	January 10, 2000 1/10/00	== 4.3.2
CVE-1999-1117	Low	December 31, 1999 12/31/99	== 4.2 == 4.1
CVE-1999-1589	High	December 31, 1999 12/31/99	== 1.2.1 == 3.1 == 2.2.1 == 1.3 == 3.2
CVE-1999-0835	High	November 10, 1999 11/10/99	== 4.3
CVE-1999-0851	Low	November 10, 1999 11/10/99	== 4.3
CVE-1999-0903	High	October 26, 1999 10/26/99	== 4.3.2
CVE-1999-1583	High	September 30, 1999 9/30/99	== 4.3
CVE-1999-0789	High	September 28, 1999 9/28/99	== 4.3.2 == 4.3 == 4.3.1
CVE-1999-1013	High	September 23, 1999 9/23/99	== 4.2.1 == 4.1.5
CVE-1999-0687	High	September 13, 1999 9/13/99	== 4.3.2 == 4.3 == 4.2.1 == 4.1.4 == 4.2 == 4.1.5 == 4.1.1 == 4.1.2 == 4.3.1 == 4.1 == 4.1.3
CVE-1999-0691	High	September 13, 1999 9/13/99	== 4.3.2 == 4.3 == 4.2.1 == 4.1.4 == 4.2 == 4.1.5 == 4.1.1 == 4.1.2 == 4.3.1 == 4.1 == 4.1.3
CVE-1999-0745	High	August 18, 1999 8/18/99	== 3.2.5 == 3.2.4 == 3.1 == 2.2.1 == 3.2
CVE-1999-0694	Low	August 11, 1999 8/11/99	== 4.3 == 4.2
CVE-1999-1079	Low	May 6, 1999 5/6/99	== 4.3.2 == 4.3 == 4.2.1 == 3.2.5 == 4.1.4 == 4.2 == 4.1.5 == 4.1.1 == 4.1.2 == 4.1 == 4.1.3
CVE-1999-1405	High	February 17, 1999 2/17/99	== 4.2.1 == 3.2.5 == 4.1.4 == 4.2 == 4.1.5 == 4.1.2 == 4.1 == 4.1.3
CVE-1999-0057	High	November 16, 1998 11/16/98	*
CVE-1999-0118	High	November 1, 1998 11/1/98	== 4.3 == 4.2 == 4.1 == 3.2
CVE-1999-0088	High	October 26, 1998 10/26/98	== 4.3
CVE-1999-1574	High	July 6, 1998 7/6/98	== 4.3.0
CVE-1999-1480	Low	June 11, 1998 6/11/98	== 4.3
CVE-1999-0055	High	May 14, 1998 5/14/98	== 4.3.2 == 4.3 == 4.2.1 == 4.2 == 4.3.1
CVE-1999-0009	High	April 8, 1998 4/8/98	== 4.3 == 4.2.1 == 4.1.4 == 4.2 == 4.1.5 == 4.1.1 == 4.1.2 == 4.1 == 4.1.3
CVE-1999-0010	Medium	April 8, 1998 4/8/98	== 4.3 == 4.2 == 4.1
CVE-1999-0011	Medium	April 8, 1998 4/8/98	== 4.3 == 4.2 == 4.1
CVE-1999-0003	High	April 1, 1998 4/1/98	== 4.3 == 4.2.1 == 4.1.4 == 4.2 == 4.1.5 == 4.1.1 == 4.1.2 == 4.1 == 4.1.3
CVE-1999-1075	Medium	March 18, 1998 3/18/98	== 4.1.5
CVE-1999-1486	Low	February 25, 1998 2/25/98	== 4.3 == 4.2.1 == 4.1.4 == 4.2 == 4.1.5 == 4.1.1 == 4.1.2 == 4.1 == 4.1.3
CVE-1999-0087	Medium	February 1, 1998 2/1/98	== 4.3 == 4.2 == 4.1
CVE-1999-0014	High	January 21, 1998 1/21/98	== 4.3 == 4.2 == 4.1
CVE-1999-1487	High	January 21, 1998 1/21/98	== 4.3 == 4.2.1 == 4.1.4 == 4.2 == 4.1.5 == 4.1.1 == 4.1.2 == 4.1 == 4.1.3
CVE-1999-0086	Medium	January 8, 1998 1/8/98	== 4.3 == 4.2 == 4.1 == 3.2
CVE-1999-0513	Medium	January 5, 1998 1/5/98	== 3.2.5 == 3.2.4 == 3.1 == 3.2
CVE-1999-0017	High	December 10, 1997 12/10/97	== 4.3 == 4.2 == 4.1 == 3.2
CVE-1999-0018	High	December 5, 1997 12/5/97	== 4.1 == 3.2
CVE-1999-0092	High	October 29, 1997 10/29/97	== 4.2.1
CVE-1999-0093	High	October 29, 1997 10/29/97	== 4.1.4 == 4.2 == 4.1.5 == 4.1.1 == 4.1.2 == 4.1 == 4.1.3
CVE-1999-0094	Low	October 29, 1997 10/29/97	== 4.1.4 == 4.2 == 4.1.5 == 4.1.1 == 4.1.2 == 4.1 == 4.1.3
CVE-1999-0097	High	October 29, 1997 10/29/97	== 4.2.1 == 3.2.5 == 3.2.4 == 4.1.4 == 4.2 == 4.1.5 == 4.1.1 == 4.1.2 == 4.1 == 4.1.3 == 3.2
CVE-1999-0089	High	October 28, 1997 10/28/97	== 4.3
CVE-1999-0091	High	October 28, 1997 10/28/97	== 4.2.1 == 4.1.4 == 4.2 == 4.1.5 == 4.1.1 == 4.1.2 == 4.1 == 4.1.3
CVE-1999-0072	High	October 22, 1997 10/22/97	== 4.2.1 == 4.1.4 == 4.2 == 4.1.5 == 4.1.1 == 4.1.2 == 4.1 == 4.1.3

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.