Privoxy up to 3.0.20 Proxy-Authentication Header input validation

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 identified as problematic has been detected in Privoxy. Impacted is an unknown function of the component Proxy-Authentication Header. Performing a manipulation results in input validation. This vulnerability is reported as CVE-2013-2503. Moreover, an exploit is present. You should upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic has been found in Privoxy. This affects some unknown functionality of the component Proxy-Authentication Header. The manipulation with an unknown input leads to a input validation vulnerability. CWE is classifying the issue as CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. This is going to have an impact on confidentiality. The summary by CVE is:

Privoxy before 3.0.21 does not properly handle Proxy-Authenticate and Proxy-Authorization headers in the client-server data stream, which makes it easier for remote HTTP servers to spoof the intended proxy service via a 407 (aka Proxy Authentication Required) HTTP status code.

The bug was discovered 03/05/2013. The weakness was disclosed 03/11/2013 by Chris John Riley as CVE-2013-2503 as not defined mailinglist post (Bugtraq). It is possible to read the advisory at seclists.org. The public release has been coordinated in cooperation with the project team. This vulnerability is uniquely identified as CVE-2013-2503 since 03/07/2013. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are unknown but a public exploit is available.

A public exploit has been developed by Chris John Riley and been published immediately after the advisory. The exploit is shared for download at c22.cc. It is declared as proof-of-concept. The vulnerability scanner Nessus provides a plugin with the ID 74941 (openSUSE Security Update : privoxy (openSUSE-2013-242)), 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 165905 (SUSE Security Update for privoxy (openSUSE-SU-2013:0564-1)).

Upgrading to version 3.0.21 eliminates this vulnerability. A possible mitigation has been published even before and not after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (82726), Exploit-DB (38377), Tenable (74941), SecurityFocus (BID 58425†) and OSVDB (91126†). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

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: Input validation
CWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Author: Chris John Riley
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 74941
Nessus Name: openSUSE Security Update : privoxy (openSUSE-2013-242)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Port: 🔍

OpenVAS ID: 865487
OpenVAS Name: Fedora Update for privoxy FEDORA-2013-3753
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: Privoxy 3.0.21

Timelineinfo

03/10/2011 🔍
03/05/2013 +726 days 🔍
03/07/2013 +2 days 🔍
03/11/2013 +4 days 🔍
03/11/2013 +0 days 🔍
03/11/2013 +0 days 🔍
03/11/2013 +0 days 🔍
03/11/2013 +0 days 🔍
03/12/2013 +1 days 🔍
03/24/2013 +12 days 🔍
06/13/2014 +446 days 🔍
02/03/2025 +3888 days 🔍

Sourcesinfo

Advisory: CVE-2013-2503
Researcher: Chris John Riley
Status: Confirmed
Confirmation: 🔍
Coordinated: 🔍

CVE: CVE-2013-2503 (🔍)
GCVE (CVE): GCVE-0-2013-2503
GCVE (VulDB): GCVE-100-7947
X-Force: 82726
SecurityFocus: 58425 - Privoxy Proxy Authentication Information Disclosure Vulnerabilities
OSVDB: 91126
Vulnerability Center: 38875 - Privoxy Before 3.0.21 Remote Spoofing Vulnerability via 407 HTTP Status Code, Medium

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

Entryinfo

Created: 03/12/2013 14:56
Updated: 02/03/2025 09:23
Changes: 03/12/2013 14:56 (81), 04/26/2017 17:39 (2), 05/06/2021 08:24 (3), 12/27/2024 01:42 (18), 02/03/2025 09:23 (1)
Complete: 🔍
Committer:
Cache ID: 216:DDC:103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Interested in the pricing of exploits?

See the underground prices here!