CVE-2024-52532

What it actually does

Infinite loop during WebSocket frame parsing causes unbounded memory allocation and CPU consumption in libsoup clients or servers.

Why it matters to the business

Applications using the library become unresponsive or crash under load, leading to service outages and increased infrastructure costs until the component is updated.

How an attack unfolds

An attacker establishes a WebSocket connection and sends a sequence of specially crafted data frames that trigger the parsing loop, exhausting resources on the target process without authentication.

How to fix it

Upgrade GNOME libsoup to version 3.6.1 or later, or apply commit 8b46a93bc1cbadb22dcdbb6844d9616723376535 in source builds. Restart affected services after the update.

How to confirm the fix worked

Confirm the installed libsoup version is at least 3.6.1; run regression tests that exercise WebSocket frame parsing with boundary-case payloads; monitor process memory and CPU under load.

Typical attack path

1. Establish WebSocket connection to the vulnerable endpoint
2. Transmit crafted data patterns that match the infinite-loop condition
3. Observe resource exhaustion on the target process
4. Repeat or sustain traffic to maintain denial of service

How to detect it

Search application and system logs for sudden spikes in memory or CPU usage tied to WebSocket-handling processes; review process listings for sustained high-resource consumption after WebSocket activity begins.

What your security team should do

• Prioritize upgrade of all libsoup instances to the fixed commit or 3.6.1 within standard change windows
• Add WebSocket traffic monitoring for anomalous frame patterns in application logs
• Review dependent projects for direct or transitive use of the library and schedule coordinated updates