CVE-2013-2503
Last modified
CVE-2013-2503 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 4.63% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Privoxy | Privoxy | <= 3.0.20 | Beta |
| Privoxy | Privoxy | 2.9.0 | Pre-Alpha |
| Privoxy | Privoxy | 2.9.1 | Pre-Alpha |
| Privoxy | Privoxy | 2.9.2 | Pre-Alpha |
| Privoxy | Privoxy | 2.9.3 | Pre-Alpha |
| Privoxy | Privoxy | 2.9.11 | Alpha |
| Privoxy | Privoxy | 2.9.12 | Beta |
| Privoxy | Privoxy | 2.9.13 | Beta |
| Privoxy | Privoxy | 2.9.14 | Beta |
| Privoxy | Privoxy | 2.9.16 | — |
| Privoxy | Privoxy | 2.9.18 | — |
| Privoxy | Privoxy | 3.0 | — |
| Privoxy | Privoxy | 3.0.2 | — |
| Privoxy | Privoxy | 3.0.3 | — |
| Privoxy | Privoxy | 3.0.5 | Beta |
| Privoxy | Privoxy | 3.0.6 | — |
| Privoxy | Privoxy | 3.0.7 | Beta |
| Privoxy | Privoxy | 3.0.8 | — |
| Privoxy | Privoxy | 3.0.9 | Beta |
| Privoxy | Privoxy | 3.0.10 | — |
| Privoxy | Privoxy | 3.0.11 | — |
| Privoxy | Privoxy | 3.0.12 | — |
| Privoxy | Privoxy | 3.0.13 | Beta |
| Privoxy | Privoxy | 3.0.14 | Beta |
| Privoxy | Privoxy | 3.0.15 | Beta |
| Privoxy | Privoxy | 3.0.16 | — |
| Privoxy | Privoxy | 3.0.17 | — |
| Privoxy | Privoxy | 3.0.18 | — |
| Privoxy | Privoxy | 3.0.19 | — |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2013-2503?
How severe is CVE-2013-2503?
How do I fix CVE-2013-2503?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2013
- CVE-2013-2494libdns in ISC DHCP 4.2.x before 4.2.5-P1 allows remote name …
- CVE-2013-2495The iff_read_header function in iff.c in libavformat in FFmp…
- CVE-2013-2496The msrle_decode_8_16_24_32 function in msrledec.c in libavc…
- CVE-2013-2498SQL injection vulnerability in the login page in flexycms/mo…
- CVE-2013-2499SimpleHRM 2.3 and earlier could allow remote attackers to by…7.5
- CVE-2013-2501Cross-site scripting (XSS) vulnerability in the Terillion Re…
- CVE-2013-2504Cross-site scripting (XSS) vulnerability in SPS/Portal/defau…
- CVE-2013-2506app/models/spree/user.rb in spree_auth_devise in Spree 1.1.x…
- CVE-2013-2507Multiple cross-site scripting (XSS) vulnerabilities in the B…
- CVE-2013-2512The ftpd gem 0.2.1 for Ruby allows remote attackers to execu…9.8
- CVE-2013-2513The flash_tool gem through 0.6.0 for Ruby allows command exe…9.8
- CVE-2013-2516Vulnerability in FileUtils v0.7, Ruby Gem Fileutils <= v0.7 …
Are you affected by CVE-2013-2503?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST