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.

326,972

Total vulnerabilities in the database

Vulnerabilities for products matching "lighttpd"

Found 1 matching product.

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

lighttpd / lighttpd

35 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2025-12642	Critical	November 3, 2025 11/3/25	== 1.4.80
CVE-2022-41556	High	October 6, 2022 10/6/22	>= 1.4.56 < 1.4.67
CVE-2022-37797	High	September 12, 2022 9/12/22	== 1.4.65
CVE-2022-30780	High	June 11, 2022 6/11/22	== 1.4.57 == 1.4.58 == 1.4.56
CVE-2022-22707	Medium	January 6, 2022 1/6/22	>= 1.4.46 <= 1.4.63
CVE-2019-11072	High	April 10, 2019 4/10/19	<= 1.4.53
CVE-2018-19052	High	November 7, 2018 11/7/18	< 1.4.50
CVE-2015-3200	Medium	June 9, 2015 6/9/15	<= 1.4.35
CVE-2014-2323	Critical	March 14, 2014 3/14/14	< 1.4.35
CVE-2014-2324	Medium	March 14, 2014 3/14/14	< 1.4.35
CVE-2013-4559	High	November 20, 2013 11/20/13	< 1.4.33
CVE-2013-4560	Medium	November 20, 2013 11/20/13	< 1.4.33
CVE-2013-4508	High	November 8, 2013 11/8/13	>= 1.4.24 <= 1.4.33
CVE-2013-1427	Low	March 21, 2013 3/21/13	<= 1.4.27 == 1.3.16 == 1.4.3 == 1.4.4 == 1.4.5 == 1.4.6 == 1.4.7 == 1.4.8 == 1.4.9 == 1.4.10 == 1.4.11 == 1.4.12 == 1.4.13 == 1.4.15 == 1.4.16 == 1.4.18 == 1.4.19 == 1.4.20 == 1.4.21 == 1.4.22 == 1.4.23 == 1.4.24 == 1.4.25 == 1.4.26
CVE-2012-5533	Medium	November 24, 2012 11/24/12	== 1.4.32 == 1.4.31
CVE-2011-4362	Medium	December 24, 2011 12/24/11	== 1.5.0 >= 1.4.1 < 1.4.30
CVE-2010-0295	Medium	February 3, 2010 2/3/10	== 1.4.3 == 1.2.3 == 1.4.21 == 1.2.5 == 1.4.18 == 1.3.6 == 1.3.12 == 1.3.15 == 1.2.2 == 1.3.0 == 1.0.3 == 1.4.8 == 1.1.6 == 1.4.17 == 1.4.4 == 1.1.5 == 1.4.24 == 1.3.9 == 1.3.5 == 1.1.1 == 1.2.8 == 1.3.13 == 1.2.6 == 1.3.4 == 1.4.11 == 1.4.2 == 1.4.19 == 1.2.1 == 1.3.14 == 1.1.4 == 1.4.23 == 1.1.9 == 1.5.0 == 1.4.20 == 1.4.14 == 1.4.10 == 1.1.3 == 1.4.5 == 1.1.0 == 1.3.3 == 1.4.16 == 1.3.8 == 1.0.2 == 1.1.7 <= 1.4.25 == 1.2.0 == 1.1.8 == 1.3.11 == 1.3.16 == 1.3.1 == 1.4.12 == 1.4.9 == 1.3.10 == 1.1.2 == 1.4.7 == 1.4.6 == 1.4.22 == 1.2.7 == 1.4.15 == 1.4.13 == 1.3.2 == 1.4.0
CVE-2008-4359	High	October 3, 2008 10/3/08	< 1.4.20
CVE-2008-4360	High	October 3, 2008 10/3/08	< 1.4.20
CVE-2008-4298	Medium	September 27, 2008 9/27/08	== 1.4.3 == 1.2.3 == 1.2.5 == 1.4.18 == 1.3.6 == 1.3.12 == 1.3.15 == 1.4.1 == 1.2.2 == 1.3.0 <= 1.4.19 == 1.4.8 == 1.1.6 == 1.4.17 == 1.4.4 == 1.1.5 == 1.3.9 == 1.2.4 == 1.3.5 == 1.1.1 == 1.2.8 == 1.3.13 == 1.2.6 == 1.3.4 == 1.4.11 == 1.4.2 == 1.2.1 == 1.3.14 == 1.1.4 == 1.1.9 == 1.4.14 == 1.4.10 == 1.1.3 == 1.4.5 == 1.3.3 == 1.4.16 == 1.3.8 == 1.1.7 == 1.1.8 == 1.3.11 == 1.3.16 == 1.3.1 == 1.4.12 == 1.4.9 == 1.3.10 == 1.1.2 == 1.4.7 == 1.4.6 == 1.2.7 == 1.4.15 == 1.3.7 == 1.4.13 == 1.3.2 == 1.4.0
CVE-2008-1531	Low	March 27, 2008 3/27/08	<= 1.4.19 >= 1.5 < 1.5.0
CVE-2008-1270	Medium	March 10, 2008 3/10/08	<= 1.4.18
CVE-2008-1111	Medium	March 4, 2008 3/4/08	== 1.4.18
CVE-2008-0983	Medium	February 26, 2008 2/26/08	== 1.4.18 == 1.4.8 == 1.4.17 == 1.4.11 == 1.4.14 == 1.4.10 == 1.4.16 == 1.4.12 == 1.4.9 == 1.4.7 == 1.4.15 == 1.4.13
CVE-2007-4727	Medium	September 12, 2007 9/12/07	<= 1.4.15
CVE-2007-3946	Medium	July 24, 2007 7/24/07	<= 1.4.15
CVE-2007-3947	Medium	July 24, 2007 7/24/07	<= 1.4.15
CVE-2007-3948	Low	July 24, 2007 7/24/07	<= 1.4.15
CVE-2007-3949	High	July 24, 2007 7/24/07	<= 1.4.15
CVE-2007-3950	Low	July 24, 2007 7/24/07	<= 1.4.15
CVE-2007-1869	Medium	April 18, 2007 4/18/07	== 1.4.12 == 1.4.13
CVE-2007-1870	High	April 18, 2007 4/18/07	== 1.4.3 == 1.3.6 == 1.3.12 == 1.3.15 == 1.4.1 == 1.3.0 == 1.4.8 == 1.4.4 == 1.3.9 == 1.3.5 == 1.3.13 == 1.3.4 == 1.4.2 == 1.3.14 == 1.4.10 == 1.4.5 == 1.3.3 == 1.3.8 == 1.3.11 == 1.3.16 == 1.3.1 == 1.4.12 == 1.4.9 == 1.3.10 == 1.4.7 == 1.4.6 == 1.3.7 == 1.4.13 == 1.3.2 == 1.4.0
CVE-2006-0814	Medium	March 6, 2006 3/6/06	== 1.4.3 == 1.2.3 == 1.2.5 == 1.3.6 == 1.3.12 == 1.3.15 == 1.4.1 == 1.2.2 == 1.3.0 == 1.0.3 == 1.4.8 == 1.1.6 == 1.4.4 == 1.1.5 == 1.3.9 == 1.2.4 == 1.3.5 == 1.1.1 == 1.2.8 == 1.3.13 == 1.2.6 == 1.3.4 == 1.4.2 == 1.2.1 == 1.3.14 == 1.1.4 == 1.1.9 == 1.4.10 == 1.1.3 == 1.4.5 == 1.1.0 == 1.3.3 == 1.3.8 == 1.0.2 == 1.1.7 == 1.2.0 == 1.1.8 == 1.3.11 == 1.3.16 == 1.3.1 == 1.4.9 == 1.3.10 == 1.1.2 == 1.4.7 == 1.4.6 == 1.2.7 == 1.3.7 == 1.3.2 == 1.4.0
CVE-2006-0760	Low	February 18, 2006 2/18/06	== 1.4.3 == 1.2.3 == 1.2.5 == 1.3.6 == 1.3.12 == 1.3.15 == 1.4.1 == 1.2.2 == 1.3.0 == 1.0.3 == 1.4.8 == 1.1.6 == 1.4.4 == 1.1.5 == 1.3.9 == 1.2.4 == 1.3.5 == 1.1.1 == 1.2.8 == 1.3.13 == 1.2.6 == 1.3.4 == 1.4.2 == 1.2.1 == 1.3.14 == 1.1.4 == 1.1.9 == 1.1.3 == 1.4.5 == 1.1.0 == 1.3.3 == 1.3.8 == 1.0.2 == 1.1.7 == 1.2.0 == 1.1.8 == 1.3.11 == 1.3.16 == 1.3.1 == 1.3.10 == 1.1.2 == 1.4.7 == 1.4.6 == 1.2.7 == 1.3.7 == 1.3.2 == 1.4.0
CVE-2005-0453	Medium	February 16, 2005 2/16/05	== 1.3.7

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.