Pps.jussieu Polipo 0.9.8/0.9.12/1.0.4 client.c httpClientDiscardBody 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.
5.0$0-$5k0.00

Summaryinfo

A vulnerability classified as problematic has been found in Pps.jussieu Polipo 0.9.8/0.9.12/1.0.4. This affects the function httpClientDiscardBody of the file client.c. This manipulation causes numeric error. This vulnerability is registered as CVE-2009-4413. Furthermore, an exploit is available.

Detailsinfo

A vulnerability has been found in Pps.jussieu Polipo 0.9.8/0.9.12/1.0.4 and classified as problematic. Affected by this vulnerability is the function httpClientDiscardBody of the file client.c. The manipulation with an unknown input leads to a numeric error vulnerability. The CWE definition for the vulnerability is CWE-189. As an impact it is known to affect availability. The summary by CVE is:

The httpClientDiscardBody function in client.c in Polipo 0.9.8, 0.9.12, 1.0.4, and possibly other versions, allows remote attackers to cause a denial of service (crash) via a request with a large Content-Length value, which triggers an integer overflow, a signed-to-unsigned conversion error with a negative value, and a segmentation fault.

The weakness was published 12/07/2009 by Raphael Geissert (Website). It is possible to read the advisory at openwall.com. This vulnerability is known as CVE-2009-4413 since 12/23/2009. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known.

A public exploit has been developed by Jeremy Brown and been published immediately after the advisory. It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. The vulnerability scanner Nessus provides a plugin with the ID 44866 (Debian DSA-2002-1 : polipo - denial of service), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Debian Local Security Checks. The commercial vulnerability scanner Qualys is able to test this issue with plugin 175081 (Debian Security Update for Polipo (DSA-2002)).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the databases at Exploit-DB (10338), Tenable (44866), SecurityFocus (BID 37463†), OSVDB (60808†) and Secunia (SA37607†). Similar entry is available at VDB-51290. Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 5.0

VulDB Base Score: 5.3
VulDB Temp Score: 5.0
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: Jeremy Brown
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 44866
Nessus Name: Debian DSA-2002-1 : polipo - denial of service
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍

OpenVAS ID: 100379
OpenVAS Name: Polipo Malformed HTTP GET Request Memory Corruption Vulnerability
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Exploit-DB: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍
Exploit Delay Time: 🔍

Timelineinfo

12/07/2009 🔍
12/07/2009 +0 days 🔍
12/07/2009 +0 days 🔍
12/08/2009 +1 days 🔍
12/08/2009 +0 days 🔍
12/23/2009 +14 days 🔍
12/24/2009 +1 days 🔍
12/24/2009 +0 days 🔍
12/24/2009 +0 days 🔍
03/02/2010 +68 days 🔍
03/18/2015 +1842 days 🔍
02/22/2025 +3629 days 🔍

Sourcesinfo

Advisory: openwall.com
Researcher: Raphael Geissert
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2009-4413 (🔍)
GCVE (CVE): GCVE-0-2009-4413
GCVE (VulDB): GCVE-100-51295

OVAL: 🔍

SecurityFocus: 37463 - Polipo Multiple Remote Denial Of Service Vulnerabilities
Secunia: 37607 - Polipo Multiple Denial of Service Vulnerabilities, Less Critical
OSVDB: 60808 - Polipo client.c httpClientDiscardBody() Function Signedness Error Remote DoS
Vulnerability Center: 24949 - Polipo 0.9-1.0.4 Integer Overflow Remote DoS Vulnerability via a Large Content-Length Request, Medium

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

Entryinfo

Created: 03/18/2015 15:15
Updated: 02/22/2025 20:35
Changes: 03/18/2015 15:15 (63), 02/21/2017 17:23 (20), 08/30/2021 10:03 (3), 12/15/2024 14:24 (14), 02/22/2025 20:35 (2)
Complete: 🔍
Cache ID: 216::103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!