Lighttpd vulnerabilitiesNone on the known-exploited list.
Lighttpd has 34 published vulnerabilities across 2 products in our catalogue. None of them is on the list of flaws known to be exploited today. The most affected product is Lighttpd, with 34. If you run Lighttpd software, patch the exploited flaws first.
We keep watching the known-exploited list.
Which Lighttpd products have the most vulnerabilities?
Lighttpd leads with 34 published vulnerabilities. Open a product to see its versions and which of its flaws criminals are already using.
Which Lighttpd vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Lighttpd's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Lighttpd flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 74%CVE-2019-11072Critical
lighttpd before 1.4.54 has a signed integer overflow, which might allow remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via a malicious HTTP GET request, as...
- 63%CVE-2014-2323Critical
SQL injection vulnerability in mod_mysql_vhost.c in lighttpd before 1.4.35 allows remote attackers to execute arbitrary SQL commands via the host name, related to request_check_hostname.
- 57%CVE-2022-30780High
Lighttpd 1.4.56 through 1.4.58 allows a remote attacker to cause a denial of service (CPU consumption from stuck connections) because connection_read_header_more in connections.c has a typo that disrupts use of...
- 30%CVE-2014-2324Medium
Multiple directory traversal vulnerabilities in (1) mod_evhost and (2) mod_simple_vhost in lighttpd before 1.4.35 allow remote attackers to read arbitrary files via a ..
- 21%CVE-2011-4362Medium
Integer signedness error in the base64_decode function in the HTTP authentication functionality (http_auth.c) in lighttpd 1.4 before 1.4.30 and 1.5 before SVN revision 2806 allows remote attackers to cause a denial...
- 14%CVE-2018-19052High
An issue was discovered in mod_alias_physical_handler in mod_alias.c in lighttpd before 1.4.50.
- 13%CVE-2007-4727Medium
Buffer overflow in the fcgi_env_add function in mod_proxy_backend_fastcgi.c in the mod_fastcgi extension in lighttpd before 1.4.18 allows remote attackers to overwrite arbitrary CGI variables and execute arbitrary...
- 12%CVE-2010-0295Medium
lighttpd before 1.4.26, and 1.5.x, allocates a buffer for each read operation that occurs for a request, which allows remote attackers to cause a denial of service (memory consumption) by breaking a request into...
- 12%CVE-2012-5533Medium
The http_request_split_value function in request.c in lighttpd before 1.4.32 allows remote attackers to cause a denial of service (infinite loop) via a request with a header containing an empty token, as demonstrated...
- 12%CVE-2008-1270Medium
mod_userdir in lighttpd 1.4.18 and earlier, when userdir.path is not set, uses a default of $HOME, which might allow remote attackers to read arbitrary files, as demonstrated by accessing the ~nobody directory.
All Lighttpd products we track.
2 products, most vulnerabilities first. Find the ones you run, then open a product to see its versions and exploited flaws.
Running Lighttpd? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
lighttpd before 1.4.54 has a signed integer overflow, which might allow remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via a malicious HTTP GET request, as demonstrated by mishandling of /%2F? in burl_normalize_2F_to_slash_fix in burl.c. NOTE: The developer states "The feature which can be abused to cause the crash is a new feature in lighttpd 1.4.50, and is not enabled by default. It must be explicitly configured in the config file (e.g. lighttpd.conf). Certain input will trigger an abort() in lighttpd when that feature is enabled. lighttpd detects the underflow or realloc() will fail (in both 32-bit and 64-bit executables), also detected in lighttpd. Either triggers an explicit abort() by lighttpd. This is not exploitable beyond triggering the explicit abort() with subsequent application exit.
- Matched to
- Lighttpd on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
Our catalogue lists 34 published vulnerabilities across 2 products and 108 versions from Lighttpd.
None of Lighttpd's vulnerabilities is on the list of flaws known to be exploited today.
Lighttpd, with 34 published vulnerabilities. Its own page lists the ones known to be exploited.
Create a Precursor Intelligence account and track the Lighttpd products you run. We match them against every published flaw, give each one a risk score from 0 to 100 and tell you as soon as we spot one that affects you, by email, in the app or by webhook.