This page lists publicly disclosed CVE vulnerabilities affecting libproxy_project libproxy (linked via NVD CPE). Each row includes severity scores, summaries, and publication dates to help identify and analyze security issues.
| CVE | Summary | Source | Max CVSS | EPSS % | Published | Updated |
|---|---|---|---|---|---|---|
| CVE-2020-26154 | url.cpp in libproxy through 0.4.15 is prone to a buffer overflow when PAC is enabled, as demonstrated by a large PAC file that is delivered without a Content-length header. | [email protected] | 9.8 | 3.53% | 2020-09-30 | 2026-06-16 |
| CVE-2020-25219 | url::recvline in url.cpp in libproxy 0.4.x through 0.4.15 allows a remote HTTP server to trigger uncontrolled recursion via a response composed of an infinite stream that lacks a newline character. This leads to stack exhaustion. | [email protected] | 7.5 | 4.28% | 2020-09-09 | 2026-06-16 |
| CVE-2012-5580 | Format string vulnerability in the print_proxies function in bin/proxy.c in libproxy 0.3.1 might allow context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via format string specifiers in a proxy name, as demonstrated using the http_proxy environment variable or a PAC file. | [email protected] | 7.5 | 3.12% | 2014-10-27 | 2026-06-16 |
| CVE-2012-4505 | Heap-based buffer overflow in the px_pac_reload function in lib/pac.c in libproxy 0.2.x and 0.3.x allows remote servers to have an unspecified impact via a crafted Content-Length size in an HTTP response header for a proxy.pac file request, a different vulnerability than CVE-2012-4504. | [email protected] | 10.0 | 3.22% | 2012-11-11 | 2026-06-16 |
| CVE-2012-4504 | Stack-based buffer overflow in the url::get_pac function in url.cpp in libproxy 0.4.x before 0.4.9 allows remote servers to have an unspecified impact via a large proxy.pac file. | [email protected] | 10.0 | 3.48% | 2012-11-11 | 2026-06-16 |