A vulnerability has been discovered in lighttpd which could result in denial of service.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| www-servers/lighttpd | * | < 1.4.67 | >= 1.4.67 |
Lighttpd is a lightweight high-performance web server.
Lighttpd's mod_wstunnel does not initialize a handler function pointer if an invalid HTTP request (websocket handshake) is received.
An attacker can trigger a denial of service via making Lighttpd try to call an uninitialized function pointer.
There is no known workaround at this time.
All lighttpd users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=www-servers/lighttpd-1.4.67"
Multiple vulnerabilities have been found in lighttpd, allowing remote attackers cause a Denial of Service condition or execute arbitrary SQL statements.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| www-servers/lighttpd | * | < 1.4.35 | >= 1.4.35 |
lighttpd is a lightweight high-performance web server.
Multiple vulnerabilities have been discovered in lighttpd. Please review the CVE identifiers referenced below for details.
A remote attacker could create a Denial of Service condition. Futhermore, a remote attacker may be able to execute arbitrary SQL statements.
There is no known workaround at this time.
All lighttpd users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=www-servers/lighttpd-1.4.35"
A processing error in lighttpd might result in a Denial of Service condition.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| www-servers/lighttpd | * | < 1.4.25-r1 | >= 1.4.25-r1 |
lighttpd is a lightweight high-performance web server.
Li Ming reported that lighttpd does not properly process packets that are sent overly slow.
A remote attacker might send specially crafted packets to a server running lighttpd, possibly resulting in a Denial of Service condition via host memory exhaustion.
There is no known workaround at this time.
All lighttpd users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=www-servers/lighttpd-1.4.25-r1"
Multiple vulnerabilities in lighttpd may lead to information disclosure or a Denial of Service.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| www-servers/lighttpd | * | < 1.4.20 | >= 1.4.20 |
lighttpd is a lightweight high-performance web server.
Multiple vulnerabilities have been reported in lighttpd:
A remote attacker could exploit these vulnerabilities to cause a Denial of Service, to bypass intended access restrictions, to obtain sensitive information, or to possibly modify data.
There is no known workaround at this time.
All lighttpd users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=www-servers/lighttpd-1.4.20"
Multiple vulnerabilities in lighttpd may lead to information disclosure or a Denial of Service.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| www-servers/lighttpd | * | < 1.4.19-r2 | >= 1.4.19-r2 |
lighttpd is a lightweight high-performance web server.
Julien Cayzax discovered that an insecure default setting exists in mod_userdir in lighttpd. When userdir.path is not set the default value used is $HOME. It should be noted that the "nobody" user's $HOME is "/" (CVE-2008-1270). An error also exists in the SSL connection code which can be triggered when a user prematurely terminates his connection (CVE-2008-1531).
A remote attacker could exploit the first vulnerability to read arbitrary files. The second vulnerability can be exploited by a remote attacker to cause a Denial of Service by terminating a victim's SSL connection.
As a workaround for CVE-2008-1270 you can set userdir.path to a sensible value, e.g. "public_html".
All lighttpd users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=www-servers/lighttpd-1.4.19-r2"
Multiple vulnerabilities have been discovered in lighttpd.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| www-servers/lighttpd | * | < 1.4.18-r2 | >= 1.4.18-r2 |
lighttpd is a lightweight high-performance web server.
lighttpd contains a calculation error when allocating the global file descriptor array (CVE-2008-0983). Furthermore, it sends the source of a CGI script instead of returning a 500 error (Internal Server Error) when the fork() system call fails (CVE-2008-1111).
A remote attacker could exploit these vulnerabilities to cause a Denial of Service or gain the source of a CGI script.
There is no known workaround at this time.
All lighttpd users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=www-servers/lighttpd-1.4.18-r2"
Lighttpd is vulnerable to the remote execution of arbitrary code.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| www-servers/lighttpd | * | < 1.4.18 | >= 1.4.18 |
Lighttpd is a lightweight HTTP web server.
Mattias Bengtsson and Philip Olausson have discovered a buffer overflow vulnerability in the function fcgi_env_add() in the file mod_fastcgi.c when processing overly long HTTP headers.
A remote attacker could send a specially crafted request to the vulnerable Lighttpd server, resulting in the remote execution of arbitrary code with privileges of the user running the web server. Note that mod_fastcgi is disabled in Gentoo's default configuration.
Edit the file /etc/lighttpd/lighttpd.conf and comment the following line: "include mod_fastcgi.conf"
All Lighttpd users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=www-servers/lighttpd-1.4.18"
Several vulnerabilities were reported in Lighttpd, most of them allowing a Denial of Service and potentially the remote execution of arbitrary code.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| www-servers/lighttpd | * | < 1.4.16 | >= 1.4.16 |
Lighttpd is a lightweight HTTP web server.
Stefan Esser discovered errors with evidence of memory corruption in the code parsing the headers. Several independent researchers also reported errors involving the handling of HTTP headers, the mod_auth and mod_scgi modules, and the limitation of active connections.
A remote attacker can trigger any of these vulnerabilities by sending malicious data to the server, which may lead to a crash or memory exhaustion, and potentially the execution of arbitrary code. Additionally, access-deny settings can be evaded by appending a final / to a URL.
There is no known workaround at this time.
All Lighttpd users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=www-servers/lighttpd-1.4.16"
Two vulnerabilities have been discovered in Lighttpd, each allowing for a Denial of Service.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| www-servers/lighttpd | * | < 1.4.14 | >= 1.4.14 |
Lighttpd is a lightweight HTTP web server.
Robert Jakabosky discovered an infinite loop triggered by a connection abort when Lighttpd processes carriage return and line feed sequences. Marcus Rueckert discovered a NULL pointer dereference when a server running Lighttpd tries to access a file with a mtime of 0.
A remote attacker could upload a specially crafted file to the server or send a specially crafted request and then abort the connection, possibly resulting in a crash or a Denial of Service by CPU consumption.
There is no known workaround at this time.
All Lighttpd users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=www-servers/lighttpd-1.4.14"
An attacker can trick lighttpd into revealing the source of scripts that should be executed as CGI or FastCGI applications.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| www-servers/lighttpd | * | < 1.3.10-r1 | >= 1.3.10-r1 |
lighttpd is a small-footprint, fast, compliant and very flexible web-server which is optimized for high-performance environments.
lighttpd uses file extensions to determine which elements are programs that should be executed and which are static pages that should be sent as-is. By appending %00 to the filename, you can evade the extension detection mechanism while still accessing the file.
A remote attacker could send specific queries and access the source of scripts that should have been executed as CGI or FastCGI applications.
There is no known workaround at this time.
All lighttpd users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=www-servers/lighttpd-1.3.10-r1"