lighttpd up to 1.1.1 http_auth.c base64_decode numeric error

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.
4.8$0-$5k0.00

Summaryinfo

A vulnerability was found in lighttpd up to 1.1.1. It has been classified as problematic. This vulnerability affects the function base64_decode of the file http_auth.c. Performing a manipulation results in numeric error. This vulnerability is cataloged as CVE-2011-4362. Furthermore, there is an exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability, which was classified as problematic, was found in lighttpd up to 1.1.1 (Web Server). This affects the function base64_decode of the file http_auth.c. The manipulation with an unknown input leads to a numeric error vulnerability. CWE is classifying the issue as CWE-189. This is going to have an impact on availability. The summary by CVE is:

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 of service (segmentation fault) via crafted base64 input that triggers an out-of-bounds read with a negative index.

The weakness was shared 12/24/2011 by Xi Wang as Bug 758624 as confirmed bug report (Bugzilla). It is possible to read the advisory at bugzilla.redhat.com. This vulnerability is uniquely identified as CVE-2011-4362 since 11/04/2011. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a public exploit are known.

A public exploit has been developed by pi3 in ANSI C and been published 1 weeks after the advisory. The exploit is shared for download at securityfocus.com. It is declared as proof-of-concept. The vulnerability scanner Nessus provides a plugin with the ID 74546 (openSUSE Security Update : lighttpd (openSUSE-2012-110)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family SuSE Local Security Checks. The commercial vulnerability scanner Qualys is able to test this issue with plugin 120902 (Solaris 11 Support Repository Update (SRU) 6.6 Missing).

Upgrading to version 1.1.2 eliminates this vulnerability.

The vulnerability is also documented in the databases at X-Force (71536), Exploit-DB (18295), Tenable (74546), SecurityFocus (BID 50851†) and OSVDB (77366†). The entries VDB-4549 and VDB-59848 are related to this item. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 4.8

VulDB Base Score: 5.3
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Numeric error
CWE: CWE-189
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

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

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 74546
Nessus Name: openSUSE Security Update : lighttpd (openSUSE-2012-110)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Port: 🔍

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

Qualys ID: 🔍
Qualys Name: 🔍

Exploit-DB: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍
Exploit Delay Time: 🔍

Upgrade: lighttpd 1.1.2
ISS Proventia IPS: 🔍

Timelineinfo

11/04/2011 🔍
11/29/2011 +25 days 🔍
11/30/2011 +1 days 🔍
12/21/2011 +21 days 🔍
12/24/2011 +3 days 🔍
12/24/2011 +0 days 🔍
12/24/2011 +0 days 🔍
12/31/2011 +7 days 🔍
12/31/2011 +0 days 🔍
01/17/2012 +17 days 🔍
06/13/2014 +878 days 🔍
03/23/2015 +283 days 🔍
08/14/2024 +3432 days 🔍

Sourcesinfo

Advisory: Bug 758624
Researcher: Xi Wang
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2011-4362 (🔍)
GCVE (CVE): GCVE-0-2011-4362
GCVE (VulDB): GCVE-100-59799

OVAL: 🔍

X-Force: 71536
SecurityFocus: 50851 - lighttpd 'http_auth.c' Remote Denial of Service Vulnerability
Secunia: 47260 - Debian update for lighttpd, Moderately Critical
OSVDB: 77366
SecurityTracker: 1026359 - lighttpd Authentication Decoding Bug Lets Remote Users Deny Service
Vulnerability Center: 34233 - Lighttpd Before 1.4.30 Remote DoS Vulnerability via a Crafted Base64 Input, High

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

Entryinfo

Created: 03/23/2015 16:50
Updated: 08/14/2024 21:59
Changes: 03/23/2015 16:50 (73), 04/09/2017 13:25 (25), 11/28/2021 14:17 (3), 08/14/2024 21:59 (14)
Complete: 🔍
Cache ID: 216:E70:103

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!