PatchTheCVElibproxy vulnerabilities and fixes
Recent CVEs affecting libproxy, with upgrade or downgrade steps. 2 tracked.
libproxy has 2 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 2. Most recent: 2020-09-30. Highest priority: CVE-2020-26154 (score 67/100).
- CVE-2020-26154 CRITICAL 9.8 UPGRADE MITIGATE url.cpp in libproxy through 0.4.15 is prone to a buffer overflow when PAC is enabled, as demonstrated by a lar
- CVE-2020-25219 HIGH 7.5 UPGRADE MITIGATE url::recvline in url.cpp in libproxy 0.4.x through 0.4.15 allows a remote HTTP server to trigger uncontrolled
FAQ
How do I fix libproxy vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is libproxy being exploited right now?
None of the tracked libproxy CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which libproxy CVE should I patch first?
CVE-2020-26154 currently ranks highest (67/100): url.cpp in libproxy through 0.4.15 is prone to a buffer overflow when PAC is enabled, as demonstrated by a lar.