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

Found 2 matching products. Filters apply to all results.

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

sun / sunos

1292 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-1999-0165	High	March 1, 1997 3/1/97	== 5.3 == 4.0.1 == 4.1.4 == 4.0.3 == 4.1 == 5.4 == 4.0.2 == 4.1.1 == 4.1.3 == 3.5 == 5.0 == 4.1.2 == 4.0 == 5.1 == 5.2
CVE-1999-0318	High	March 1, 1997 3/1/97	== 5.7 == 5.8 == 5.5.1
CVE-1999-0109	High	February 10, 1997 2/10/97	== 5.5 == 5.5.1
CVE-1999-0046	High	February 6, 1997 2/6/97	== 5.3 == 4.1.4 == 5.5 == 5.4 == 5.5.1 == 4.1.3u1
CVE-1999-0298	High	February 5, 1997 2/5/97	== 4.1.4 == 4.1.3
CVE-1999-0369	High	February 1, 1997 2/1/97	== 5.3 == 4.1.4 == 5.5 == 5.4 == 5.5.1 == 4.1.3 == 5.0 == 5.1 == 5.2
CVE-1999-0966	High	January 27, 1997 1/27/97	== 5.5
CVE-1999-0051	High	January 6, 1997 1/6/97	== 4.1.4 == 4.1.4jl == 5.5 == 5.4 == 4.1.1 == 5.5.1 == 4.1.3u1 == 4.1.3 == 4.1.2
CVE-1999-0217	Medium	January 1, 1997 1/1/97	== 4.1psr_a == 4.0.3 == 4.1.3a1 == 4.1 == 4.0.3c == 4.1.1 == 4.1.3 == 4.1.2
CVE-1999-0345	Medium	January 1, 1997 1/1/97	*
CVE-1999-0517	Medium	January 1, 1997 1/1/97	== 5.0
CVE-1999-0128	Medium	December 18, 1996 12/18/96	== 5.5 == 5.4 == 5.5.1
CVE-1999-0129	Low	December 3, 1996 12/3/96	== 5.3 == 4.1.4 == 5.5 == 5.4 == 5.5.1 == 4.1.3u1
CVE-1999-0277	High	October 28, 1996 10/28/96	== 5.0
CVE-1999-0032	High	October 25, 1996 10/25/96	== 4.1.4 == 4.1.3u1
CVE-1999-0132	Low	August 15, 1996 8/15/96	== 5.3 == 5.4 == 4.1.1 == 4.1.3u1 == 4.1.3 == 5.0 == 4.1.2 == 4.1.3c == 5.1 == 5.2
CVE-1999-0134	High	August 6, 1996 8/6/96	== 5.5 == 5.4 == 5.5.1
CVE-1999-1413	Low	August 3, 1996 8/3/96	== 5.4
CVE-1999-0136	High	July 31, 1996 7/31/96	== 5.5 == 5.5.1
CVE-1999-0135	High	July 25, 1996 7/25/96	== 5.5 == 5.5.1
CVE-1999-0023	High	July 24, 1996 7/24/96	== 5.3 == 4.1.4 == 5.5 == 5.4 == 5.5.1 == 4.1.3u1 == 4.1.3
CVE-1999-0022	High	July 3, 1996 7/3/96	== 5.3 == 5.4 == 4.1.1 == 4.1.3u1 == 5.0 == 4.1.2 == 5.1 == 5.2
CVE-1999-0019	Medium	April 24, 1996 4/24/96	== 5.5 == 5.3 == 4.1.4 == 5.4 == 4.1.3
CVE-1999-0078	Low	April 18, 1996 4/18/96	== 5.5 == 4.1 == 5.4
CVE-1999-0143	Low	February 21, 1996 2/21/96	== 5.3 == 5.4
CVE-1999-0099	High	October 19, 1995 10/19/95	== 5.3 == 4.1.4 == 5.4 == 4.1.3u1 == 4.1.3
CVE-1999-0164	Medium	August 29, 1995 8/29/95	== 5.3 == 5.4
CVE-1999-1580	High	August 23, 1995 8/23/95	== 4.1.4 == 4.1.4jl == 4.1.1 == 4.1.3u1 == 4.1.3 == 4.1.2 == 4.1.3c
CVE-1999-1080	High	May 10, 1995 5/10/95	== 5.7
CVE-1999-1388	Medium	May 13, 1994 5/13/94	== 4.1
CVE-1999-0120	High	March 21, 1994 3/21/94	== 4.1
CVE-1999-0211	Medium	February 14, 1994 2/14/94	== 4.1.1 == 4.1.3 == 5.0 == 4.1.2 == 4.1.3c
CVE-1999-0334	High	December 16, 1993 12/16/93	== 5.0
CVE-1999-1137	Low	October 1, 1993 10/1/93	== 4.1 == 5.0 * <= 5.2
CVE-1999-1318	High	September 17, 1993 9/17/93	<= 4.1.3 == 4.1.1 == 4.1.3 == 4.1.2 == 4.1.3c
CVE-1999-1507	High	February 3, 1993 2/3/93	== 4.1psr_a == 4.1 == 4.1.1 == 4.1.3u1 == 4.1.3 == 4.1.2 == 4.1.3c
CVE-1999-1021	High	December 30, 1992 12/30/92	== 4.1 == 4.1.1 == 4.1.2
CVE-1999-0214	High	July 21, 1992 7/21/92	== 4.1 == 4.1.1 == 4.1.2
CVE-1999-1396	High	July 21, 1992 7/21/92	== 4.1 == 4.1.1 == 4.1.2
CVE-1999-0168	High	June 4, 1992 6/4/92	== 4.1.3 == 4.1.3c
CVE-1999-1142	High	May 27, 1992 5/27/92	<= 4.1.2
CVE-1999-0167	Low	December 6, 1991 12/6/91	== 4.1.1
CVE-1999-1468	Medium	October 22, 1991 10/22/91	== 4.1psr_a == 4.0.3 == 4.1 == 4.0.3c == 4.1.1
CVE-1999-1123	High	May 20, 1991 5/20/91	== 4.0.3 == 4.1 == 4.1.1
CVE-1999-1211	High	March 27, 1991 3/27/91	<= 4.1.1
CVE-1999-1212	High	March 27, 1991 3/27/91	== 4.0.3 == 4.0.3c
CVE-1999-1438	High	February 22, 1991 2/22/91	== 4.0.3 == 4.1 <= 4.1.1
CVE-1999-1258	Medium	January 15, 1991 1/15/91	== 4.1 <= 4.1.1
CVE-1999-1197	High	December 20, 1990 12/20/90	== 4.1.1
CVE-1999-0209	Medium	August 14, 1990 8/14/90	== 4.0.1 == 4.0.3 == 4.1 == 4.0.2 == 4.1.1 == 3.5 == 4.0

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