Improper resource allocation In libsoup3
Description
A flaw was found in libsoup's WebSocket implementation when using the permessage-deflate extension. The extension's decompression loop (inflate()) processes data in chunks without enforcing an upper boundary limit on the output buffer size. While libsoup limits the incoming compressed frame size via max_incoming_payload_size, it fails to track or limit memory allocation during decompression. A separate check for decompressed size (max_total_message_size) exists but executes only after inflation is complete, and it is entirely disabled by default for client connections. A remote, unauthenticated attacker can exploit this by sending a small, highly compressed payload (a decompression bomb), causing unbounded memory allocation that triggers an Out-of-Memory (OOM) crash and a Denial of Service (DoS).
Mitigation
Update Impact
Minimal update. May introduce new vulnerabilities or breaking changes.
Ecosystem | Component | Affected version | Patched versions |
|---|---|---|---|
debian 12 | - | ||
rpm rhel9.6 | 0:2.72.0-10.el9_6.9 | ||
rpm rhel8.4 | 0:2.62.3-2.el8_4.10 | ||
rpm rhel8.6 | 0:2.62.3-2.el8_6.10 | ||
rpm rhel10.0 | 0:3.6.5-3.el10_0.17 | ||
debian 12 | - | ||
rpm rhel6 | - | - | |
rpm rhel7 | - | - | |
rpm rhel8 | - | - | |
rpm rhel9 | 0:2.72.0-17.el9_9.6 |
1-10 of 14
10
Aliases