CVE-2020-25219: High severity Libproxy Project Libproxy vulnerability

Published Sep 9, 2020
·
Updated

Last updated 25 August 2025

Other sources

libproxy is vulnerable to a denial of service, caused by an uncontrolled recursion in url::recvline in url.cpp. By sending a specially crafted request, a remote attacker could exploit this vulnerability to cause stack exhaustion.

IBM

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.

Launchpad

Affected Software

15 affected componentsFixes available
debian/libproxy<=0.4.15-13, <=0.4.15-14, <=0.4.15-5
0.4.15-150.4.15-5+deb10u1
Libproxy Project Libproxy>=0.4.0<=0.4.15
Debian Debian Linux=9.0
Debian Debian Linux=10.0
Fedoraproject Fedora=31
Fedoraproject Fedora=32
Fedoraproject Fedora=33
openSUSE Leap=15.1
openSUSE Leap=15.2
Canonical Ubuntu Linux=16.04
Canonical Ubuntu Linux=18.04
Canonical Ubuntu Linux=20.04
IBM QRadar SIEM<=7.5 - 7.5.0 UP9 IF03
IBM QRadar Incident Forensics<=7.5 - 7.5.0 UP9 IF03
debian/libproxy
0.4.17-10.4.18-1.20.5.9-10.5.12-1

Event History

Sep 9, 2020
CVE Published
via MITRE·08:30 PM
Data Sourced
via MITRE·08:30 PM
Description
Data Sourced
via NVD·09:15 PM
DescriptionSeverityWeaknessAffected Software
Oct 17, 2024
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software
Feb 23, 2026
Data Sourced
via Ubuntu·09:32 PM
RemedyDescriptionSeverityAffected Software
Data Sourced
via Launchpad·09:33 PM
Description
Data Sourced
via Debian·09:33 PM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2020-25219?

CVE-2020-25219 has a high severity rating due to its potential to cause denial of service through stack exhaustion.

2

How do I fix CVE-2020-25219?

To mitigate CVE-2020-25219, upgrade to libproxy version 0.4.17-1 or later, depending on your distribution.

3

What software is affected by CVE-2020-25219?

CVE-2020-25219 affects libproxy versions 0.4.x up to 0.4.15, along with some IBM QRadar products running specific versions.

4

What happens if CVE-2020-25219 is exploited?

Exploitation of CVE-2020-25219 can lead to a denial of service, rendering the affected service unresponsive.

5

Is there a workaround for CVE-2020-25219?

A temporary workaround for CVE-2020-25219 may include restricting access to the affected service until a patch is applied.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203
CVE-2020-25219 - High severity Libproxy Project Libproxy vulnerability - SecAlerts