Libsoup vulnerabilitiesRanked by how likely they are to be used.
Libsoup is made by Gnome. We track 9 published vulnerabilities in it, across 307 versions. None of them is on the list of flaws known to be exploited today. If you run Libsoup, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Libsoup vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Libsoup's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Libsoup flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 23%CVE-2017-2885Critical
An exploitable stack based buffer overflow vulnerability exists in the GNOME libsoup 2.58.
- 4.2%CVE-2018-12910Critical
The get_cookies function in soup-cookie-jar.c in libsoup 2.63.2 allows attackers to have unspecified impact via an empty hostname.
- 2.8%CVE-2019-17266Critical
libsoup from versions 2.65.1 until 2.68.1 have a heap-based buffer over-read because soup_ntlm_parse_challenge() in soup-auth-ntlm.c does not properly check an NTLM message's length before proceeding with a memcpy.
- 1.9%CVE-2011-2524Medium
Directory traversal vulnerability in soup-uri.c in SoupServer in libsoup before 2.35.4 allows remote attackers to read arbitrary files via a %2e%2e (encoded dot dot) in a URI.
- 1.6%CVE-2018-11713Medium
WebCore/platform/network/soup/SocketStreamHandleImplSoup.cpp in the libsoup network backend of WebKit, as used in WebKitGTK+ prior to version 2.20.0 or without libsoup 2.62.0, unexpectedly failed to use system proxy...
- 1.6%CVE-2012-2132Medium
libsoup 2.32.2 and earlier does not validate certificates or clear the trust flag when the ssl-ca-file does not exist, which allows remote attackers to bypass authentication by connecting with a SSL connection.
- 0.9%CVE-2024-52532High
GNOME libsoup before 3.6.1 has an infinite loop, and memory consumption.
- 0.8%CVE-2024-52530High
GNOME libsoup before 3.6.0 allows HTTP request smuggling in some configurations because '\0' characters at the end of header names are ignored, i.e., a "Transfer-Encoding\0: chunked" header is treated the same as a...
- 0.7%CVE-2024-52531Medium
GNOME libsoup before 3.6.1 allows a buffer overflow in applications that perform conversion to UTF-8 in soup_header_parse_param_list_strict.
Running Libsoup? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
An exploitable stack based buffer overflow vulnerability exists in the GNOME libsoup 2.58. A specially crafted HTTP request can cause a stack overflow resulting in remote code execution. An attacker can send a special HTTP request to the vulnerable server to trigger this vulnerability.
- Matched to
- Libsoup on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 9 published vulnerabilities listed under the name Libsoup, across 307 versions.
None of Libsoup's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Libsoup. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.