lighttpd 1.4.15 request.c denial of service

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.9$0-$5k0.00

Summaryinfo

A vulnerability identified as problematic has been detected in lighttpd 1.4.15. Affected is an unknown function of the file request.c. The manipulation leads to denial of service. This vulnerability is traded as CVE-2007-3947. Furthermore, there is an exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in lighttpd 1.4.15 (Web Server) and classified as problematic. This issue affects some unknown functionality of the file request.c. The manipulation with an unknown input leads to a denial of service vulnerability. Using CWE to declare the problem leads to CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. Impacted is confidentiality, and availability. The summary by CVE is:

request.c in lighttpd 1.4.15 allows remote attackers to cause a denial of service (daemon crash) by sending an HTTP request with duplicate headers, as demonstrated by a request containing two Location header lines, which results in a segmentation fault.

The bug was discovered 06/11/2007. The weakness was shared 06/15/2007 (Website). The advisory is shared at vupen.com. The identification of this vulnerability is CVE-2007-3947 since 07/23/2007. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details as well as a public exploit are known.

A public exploit has been developed in Ruby. The exploit is available at securityfocus.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 5 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 25788 (FreeBSD : lighttpd -- multiple vulnerabilities (fc9c217e-3791-11dc-bb1a-000fea449b8a)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family FreeBSD Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 87262 (Lighttpd Multiple Vulnerabilities).

Upgrading eliminates this vulnerability. A possible mitigation has been published 2 months after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (25788), SecurityFocus (BID 24967†), OSVDB (38313†), Secunia (SA26130†) and Vulnerability Center (SBV-15934†). The entries VDB-37952, VDB-37951, VDB-37950 and VDB-37948 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.5
VulDB Meta Temp Score: 5.9

VulDB Base Score: 6.5
VulDB Temp Score: 5.9
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Denial of service
CWE: CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Programming Language: 🔍
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 25788
Nessus Name: FreeBSD : lighttpd -- multiple vulnerabilities (fc9c217e-3791-11dc-bb1a-000fea449b8a)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Nessus Port: 🔍

OpenVAS ID: 58581
OpenVAS Name: Debian Security Advisory DSA 1362-1 (lighttpd)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Timelineinfo

04/16/2007 🔍
04/16/2007 +0 days 🔍
06/11/2007 +56 days 🔍
06/15/2007 +4 days 🔍
07/20/2007 +34 days 🔍
07/20/2007 +0 days 🔍
07/21/2007 +0 days 🔍
07/23/2007 +2 days 🔍
07/23/2007 +0 days 🔍
07/27/2007 +4 days 🔍
08/28/2007 +32 days 🔍
03/15/2015 +2756 days 🔍
07/21/2021 +2320 days 🔍

Sourcesinfo

Advisory: 1869⛔
Status: Not defined
Confirmation: 🔍

CVE: CVE-2007-3947 (🔍)
GCVE (CVE): GCVE-0-2007-3947
GCVE (VulDB): GCVE-100-37949

OVAL: 🔍

SecurityFocus: 24967 - Lighttpd Multiple Code Execution, Denial of Service and Information Disclosure Vulnerabilities
Secunia: 26130
OSVDB: 38313 - lighttpd request.c Malformed HTTP Request Remote DoS
Vulnerability Center: 15934 - Lighttpd Request.c Vulnerability Allows Remote Attacker to Cause DoS, High
Vupen: ADV-2007-2585

scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍

Entryinfo

Created: 03/15/2015 15:58
Updated: 07/21/2021 10:00
Changes: 03/15/2015 15:58 (85), 07/24/2019 11:36 (4), 07/21/2021 10:00 (3)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!