dbcve.org
LibsoupApplication · Gnome

CVE-2024-52532

HIGH · 7.5 CVSS v3.1 Published 2024-11-11
Fix available
A fix is available. Upgrade to 3.6.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
GNOME libsoup before 3.6.1 has an infinite loop, and memory consumption. during the reading of certain patterns of WebSocket data from clients.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

GNOME libsoup before version 3.6.1 contains a denial-of-service vulnerability in its WebSocket implementation. When reading certain patterns of WebSocket data from clients, the library enters an infinite loop while simultaneously consuming memory, causing the affected application or service to become unresponsive or crash.

MitigationUpgrade to libsoup version 3.6.1 or later. For systems that cannot immediately upgrade, consider rate-limiting or restricting WebSocket connections as a temporary mitigation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LibsoupApplication
Affected:< 3.6.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed libsoup version
    Run a package query command appropriate for your system (for example, 'dpkg -l | grep libsoup' on Debian-based systems, or 'rpm -qa | grep libsoup' on RHEL-based systems) to list the installed libsoup package and its version number.
    Affected if The reported version is lower than 3.6.1 (for example, 3.4.0, 3.5.0, 3.6.0)
  2. Verify WebSocket support is compiled in
    Check if the libsoup library was built with WebSocket support enabled; this may be visible in pkg-config output ('pkg-config --modversion libsoup-3.0' combined with checking compile-time flags) or by inspecting the binary for websocket-related symbols.
    Affected if WebSocket support is present in the installed build
  3. Determine if WebSocket connections are accepted
    Review application or service configuration files and logs to identify whether the affected system accepts or processes incoming WebSocket connections; examine any services that link against libsoup and handle HTTP/websocket traffic.
    Affected if The system or any linked application accepts WebSocket connections from clients
  4. Confirm runtime exposure
    Monitor network listener status or service binding to confirm the application is exposed to network requests (for example, checking if a HTTP server daemon using libsoup is bound to a listening port).
    Affected if The libsoup-using service is reachable over the network and processes client requests

The environment is affected if a libsoup version below 3.6.1 is installed and any application using libsoup WebSocket functionality is accepting connections from clients.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.6.1 or later
Fixed in 3.6.1
Interim mitigation

Upgrade to libsoup version 3.6.1 or later. For systems that cannot immediately upgrade, consider rate-limiting or restricting WebSocket connections as a temporary mitigation.

Recommended fix High confidence

Libsoup 3.6.1

  1. Check the currently installed version of libsoup (e.g., dpkg -l | grep libsoup, rpm -q libsoup, or pkg-config --modversion libsoup-3.0)
  2. Update your system's package repositories to ensure you have access to the latest packages
  3. Upgrade libsoup to version 3.6.1 or later using your system's package manager (e.g., apt-get update && apt-get install libsoup-3.0-1, yum update libsoup3, or dnf update libsoup3)
  4. If building from source, download libsoup 3.6.1 or later from gitlab.gnome.org and rebuild
  5. Verify the installed version is 3.6.1 or later
  6. Restart any services or applications that use libsoup to ensure they load the updated library
Caveat Check release notes for any behavior changes; upgrading within the same major version (3.x) typically has lower risk

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Libsoup Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-52532 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-52532 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data