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.

396,888

Total vulnerabilities in the database

Vulnerabilities for products matching "linux" version 1.2.3

Found 17 matching products. Filters apply to all results.

redhat / linux

19 vulnerabilities found

Title	Severity	Date	Affected versions
CVE-2007-3103	Medium	July 15, 2007 7/15/07	`All versions`
CVE-2001-0886	Medium	December 21, 2001 12/21/01	`<= 7.2` `= 6.2` `= 7.0` `= 7.1`
CVE-2001-0889	High	December 19, 2001 12/19/01	`All versions`
CVE-2001-0690	High	September 20, 2001 9/20/01	`All versions`
CVE-2000-0701	Medium	October 20, 2000 10/20/00	`All versions`
CVE-2000-1207	High	September 30, 2000 9/30/00	`All versions`
CVE-1999-0894	High	January 4, 2000 1/4/00	`All versions`
CVE-1999-1329	High	December 31, 1999 12/31/99	`<= 5.1`
CVE-1999-1332	Low	December 31, 1999 12/31/99	`<= 5.0`
CVE-1999-1333	High	December 31, 1999 12/31/99	`<= 5.0`
CVE-1999-1335	Medium	December 31, 1999 12/31/99	`<= 4.0`
CVE-2000-0017	High	December 21, 1999 12/21/99	`All versions`
CVE-1999-1346	High	October 7, 1999 10/7/99	`<= 6.1`
CVE-1999-1347	Medium	October 7, 1999 10/7/99	`<= 6.1`
CVE-1999-1348	Low	June 30, 1999 6/30/99	`<= 6.0`
CVE-1999-0798	High	December 4, 1998 12/4/98	`All versions`
CVE-1999-1288	Medium	November 19, 1998 11/19/98	`All versions`
CVE-1999-0037	High	May 21, 1997 5/21/97	`All versions`
CVE-1999-0297	High	December 12, 1996 12/12/96	`All versions`

cyrix / linux

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected versions
CVE-1999-0403	Medium		February 1, 1999 2/1/99	`All versions`

conectiva / linux

3 vulnerabilities found

Title	Severity	Date	Affected versions
CVE-2001-0690	High	September 20, 2001 9/20/01	`All versions`
CVE-2001-0473	High	June 27, 2001 6/27/01	`All versions`
CVE-2001-0136	Medium	March 12, 2001 3/12/01	`All versions`

listmanager / linux

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected versions
CVE-2000-0863	High		November 14, 2000 11/14/00	`<= 2.96` `= 2.97` `= 2.98` `= 2.99` `= 2.100` `= 2.101` `= 2.102` `= 2.103` `= 2.104` `= 2.105.1`

gentoo / linux

87 vulnerabilities found

Title	Severity	Date	Affected versions
CVE-2014-4909	Medium	July 29, 2014 7/29/14	`All versions`
CVE-2013-0348	Low	December 13, 2013 12/13/13	`All versions`
CVE-2013-2031	Medium	November 18, 2013 11/18/13	`All versions`
CVE-2013-2032	Medium	November 18, 2013 11/18/13	`All versions`
CVE-2010-1159	Medium	October 28, 2013 10/28/13	`All versions`
CVE-2008-1383	Low	March 18, 2008 3/18/08	`All versions`
CVE-2008-1078	High	February 29, 2008 2/29/08	`All versions`
CVE-2007-1500	Medium	March 19, 2007 3/19/07	`All versions`
CVE-2006-3005	Medium	June 13, 2006 6/13/06	`All versions`
CVE-2006-0071	Medium	January 4, 2006 1/4/06	`All versions`
CVE-2005-3624	Medium	December 31, 2005 12/31/05	`All versions`
CVE-2005-3625	High	December 31, 2005 12/31/05	`All versions`
CVE-2005-3626	Medium	December 31, 2005 12/31/05	`All versions`
CVE-2005-2557	Medium	September 28, 2005 9/28/05	`All versions`
CVE-2005-1267	Medium	June 10, 2005 6/10/05	`All versions`
CVE-2005-0077	Low	May 2, 2005 5/2/05	`All versions`
CVE-2005-0988	Low	May 2, 2005 5/2/05	`All versions`
CVE-2005-1121	Medium	May 2, 2005 5/2/05	`All versions`
CVE-2005-0206	High	April 27, 2005 4/27/05	`All versions`
CVE-2005-0754	High	April 22, 2005 4/22/05	`All versions`
CVE-2004-1004	High	April 14, 2005 4/14/05	`All versions`
CVE-2004-1005	High	April 14, 2005 4/14/05	`All versions`
CVE-2004-1009	Medium	April 14, 2005 4/14/05	`All versions`
CVE-2004-1090	Medium	April 14, 2005 4/14/05	`All versions`
CVE-2004-1091	Medium	April 14, 2005 4/14/05	`All versions`
CVE-2004-1092	Medium	April 14, 2005 4/14/05	`All versions`
CVE-2004-1093	Medium	April 14, 2005 4/14/05	`All versions`
CVE-2004-1174	Medium	April 14, 2005 4/14/05	`All versions`
CVE-2004-1175	High	April 14, 2005 4/14/05	`All versions`
CVE-2004-1176	High	April 14, 2005 4/14/05	`All versions`
CVE-2005-0470	Medium	March 14, 2005 3/14/05	`All versions`
CVE-2005-0667	Medium	March 7, 2005 3/7/05	`All versions`
CVE-2004-0983	Medium	March 1, 2005 3/1/05	`All versions`
CVE-2004-0990	High	March 1, 2005 3/1/05	`All versions`
CVE-2004-1027	Medium	March 1, 2005 3/1/05	`All versions`
CVE-2004-1029	High	March 1, 2005 3/1/05	`All versions`
CVE-2004-1030	Low	March 1, 2005 3/1/05	`All versions`
CVE-2004-1031	High	March 1, 2005 3/1/05	`All versions`
CVE-2004-1032	Low	March 1, 2005 3/1/05	`All versions`
CVE-2004-1033	Low	March 1, 2005 3/1/05	`All versions`
CVE-2004-1034	High	March 1, 2005 3/1/05	`All versions`
CVE-2004-1036	Medium	March 1, 2005 3/1/05	`All versions`
CVE-2004-1037	High	March 1, 2005 3/1/05	`All versions`
CVE-2004-1052	High	March 1, 2005 3/1/05	`All versions`
CVE-2005-0535	High	February 22, 2005 2/22/05	`All versions`
CVE-2004-0937	High	February 9, 2005 2/9/05	`All versions` `= 1.4`
CVE-2004-0947	High	February 9, 2005 2/9/05	`All versions`
CVE-2004-0969	Low	February 9, 2005 2/9/05	`All versions`
CVE-2004-0972	Low	February 9, 2005 2/9/05	`All versions`
CVE-2004-0975	Low	February 9, 2005 2/9/05	`All versions`

ubuntu / linux

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected versions
CVE-2011-4613	Medium		February 5, 2014 2/5/14	`All versions`

codesys / linux

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected versions
CVE-2019-9009	High		September 17, 2019 9/17/19	`< 3.5.15.0`

Showing vulnerabilities for 17 products matching "linux". Each product has independent pagination.

Running linux on internet-facing hosts?

Knowing a product's CVEs is half the job; the other half is knowing every place it is exposed. Attack surface management continuously maps your external assets and the software they run.

What is attack surface management? →

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.