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

Found 2 matching products. Filters apply to all results.

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

suse / suse_linux

203 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2004-0592	Medium	December 31, 2004 12/31/04	== 2.6.5
CVE-2004-0802	Medium	December 31, 2004 12/31/04	== 9.2 == 9.0 == 8.2 == 8.0 == 9.1 == 8.1
CVE-2004-0817	High	December 31, 2004 12/31/04	== 9.2 == 9.0 == 8.2 == 8.0 == 9.1 == 8.1
CVE-2004-1476	Medium	December 31, 2004 12/31/04	== 9.0 == 8.0 == 9.2 == 9.1 == 8.2 == 8.1
CVE-2004-1491	Medium	December 31, 2004 12/31/04	== 6.2 == 4.0 == 9.2 == 9.0 == 7.1-alpha == 8.2 == 6.3-alpha == 5.0 == 4.4.1 == 7.2 == 8.0 == 5.2 == 3.0 == 6.0 == 6.1-alpha == 1.0 == 6.1 == 9.1 == 7.0-alpha == 4.3 == 4.4 == 5.1 == 7.0 == 7.1 == 6.3 == 6.4 == 4.2 == 6.4-alpha == 2.0 == 7.3 == 5.3 == 8.1
CVE-2004-1895	Low	December 31, 2004 12/31/04	== 9.0 == 8.2
CVE-2004-2097	Low	December 31, 2004 12/31/04	== 9.0
CVE-2004-2658	Low	December 31, 2004 12/31/04	== 9.0
CVE-2004-0803	High	December 23, 2004 12/23/04	== 9.0 == 8.2 == 8 == 1.0 == 9.1 == 8.1
CVE-2004-0867	High	December 23, 2004 12/23/04	== 9.0 == 8.2 == 8 == 1.0 == 8.1
CVE-2004-1139	Medium	December 15, 2004 12/15/04	== 9.2 == 9.0 == 8.2 == 8.0 == 9.1 == 8.1
CVE-2004-1142	Medium	December 15, 2004 12/15/04	== 9.2 == 9.0 == 8.2 == 8.0 == 9.1 == 8.1
CVE-2004-1145	Medium	December 15, 2004 12/15/04	== 9.2 == 9.0 == 8.2 == 8.0 == 9.1 == 8.1
CVE-2004-0496	High	December 6, 2004 12/6/04	== 7 == 8
CVE-2004-0497	Low	December 6, 2004 12/6/04	== 9.0 == 8.2 == 8.0 == 9.1 == 8.1
CVE-2004-0626	Medium	December 6, 2004 12/6/04	== 9.0 == 8.2 == 8.0 == 9.1 == 8.1
CVE-2004-0687	High	October 20, 2004 10/20/04	== 9.0 == 8.2 == 8 == 9.1 == 8.1
CVE-2004-0688	High	October 20, 2004 10/20/04	== 9.0 == 8.2 == 8 == 9.1 == 8.1
CVE-2004-0746	High	October 20, 2004 10/20/04	== 9.0 == 8.2 == 8 == 9.1 == 8.1
CVE-2005-0373	High	October 7, 2004 10/7/04	== 9.0 == 9.2 == 9.1 == 8.2 == 1.0 == 8.0 == 8.1
CVE-2004-0827	High	September 16, 2004 9/16/04	== 9.2 == 9.0 == 8.2 == 8.0 == 9.1 == 8.1
CVE-2004-0866	High	September 16, 2004 9/16/04	== 9.0 == 8.2 == 8 == 1.0 == 8.1
CVE-2004-0905	Low	September 14, 2004 9/14/04	== 9.0 == 8.2 == 8 == 1.0 == 9.1 == 8.1
CVE-2004-0807	Medium	September 13, 2004 9/13/04	== 9.0 == 8.2 == 8 == 9.1 == 8.1
CVE-2004-0460	High	August 6, 2004 8/6/04	== 9.0 == 8.2 == 8 == 8.0 == 7 == 9.1 == 8.1
CVE-2004-0461	High	August 6, 2004 8/6/04	== 9.0 == 8.2 == 8 == 8.0 == 7 == 9.1 == 8.1
CVE-2004-0495	High	August 6, 2004 8/6/04	== 9.0 == 8.2 == 8 == 8.0 == 7 == 9.1 == 8.1
CVE-2004-0535	Low	August 6, 2004 8/6/04	== 9.0 == 8.2 == 8 == 8.0 == 7 == 9.1 == 8.1
CVE-2004-0554	Low	August 6, 2004 8/6/04	== 9.0 == 8.2 == 8 == 8.0 == 7 == 9.1 == 8.1
CVE-2004-0587	Low	August 6, 2004 8/6/04	== 9.0 == 8 == 8.1
CVE-2004-2004	High	May 6, 2004 5/6/04	== 9.1
CVE-2004-0064	Low	February 17, 2004 2/17/04	== 9.0
CVE-2003-1295	Low	December 31, 2003 12/31/03	== 9.0
CVE-2003-1538	Medium	December 31, 2003 12/31/03	== 8 == 8.1
CVE-2003-0846	Low	November 17, 2003 11/17/03	== 7.3
CVE-2003-0847	Low	November 17, 2003 11/17/03	== 8.2
CVE-2002-2185	Low	December 31, 2002 12/31/02	== 7.1 == 7.1-alpha == 7.3 == 7.0 == 6.4 == 8.0 == 7.0-alpha == 6.4-alpha == 7.2
CVE-2002-1285	High	November 29, 2002 11/29/02	== 7.2 == 8.0 == 7.0 == 7.1 == 7.3 == 8.1
CVE-2002-0854	High	September 5, 2002 9/5/02	== 8.0 == 7.3
CVE-2002-0758	High	August 12, 2002 8/12/02	== 8.0
CVE-2002-0762	High	August 12, 2002 8/12/02	== 8.0
CVE-2002-0768	High	August 12, 2002 8/12/02	== 7.2 == 8.0 == 7.0 == 7.1 == 6.4 == 7.3
CVE-2002-0083	Critical	March 15, 2002 3/15/02	== 7.1 == 7.1-alpha == 7.3 == 7.0 == 6.4 == 7.0-alpha == 6.4-alpha == 7.2
CVE-2002-0062	High	March 8, 2002 3/8/02	== 6.2 == 7.0 == 6.3
CVE-2002-0004	High	February 27, 2002 2/27/02	== 7.1 == 7.1-alpha == 7.3 == 7.0 == 6.4 == 7.0-alpha == 6.4-alpha == 7.2
CVE-2001-0869	High	December 21, 2001 12/21/01	== 7.2 == 7.0 == 7.1 == 7.3
CVE-2001-0872	High	December 21, 2001 12/21/01	== 7.2 == 7.0 == 7.1 == 6.4 == 7.3
CVE-2001-0834	Medium	December 6, 2001 12/6/01	== 7.2 == 7.0 == 7.1 == 6.3 == 6.4 == 7.3
CVE-2001-0851	Medium	December 6, 2001 12/6/01	== 7.2 == 7.0 == 7.1 == 6.3 == 6.4 == 7.3
CVE-2001-0918	Medium	November 22, 2001 11/22/01	== 7.2 == 7.3

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