Libsoup: soupwebsocketconnection: libsoup: websocket remote denial of service via oversized control frame protocol violation
Summary
A vulnerability was found in libsoup's WebSocket frame parsing implementation. The library fails to validate length rules specified in RFC 6455 §5.5, which mandates that all WebSocket control frames (e.g., PING, PONG, CLOSE) contain a payload of 125 bytes or less. A remote, unauthenticated attacker can exploit this by sending a non-compliant, oversized control frame. Because the parser handles this protocol violation improperly instead of throwing an immediate connection termination error, it triggers a internal processing crash, resulting in a remote denial of service (DoS) for applications utilizing libsoup WebSockets. Affected products named by the advisory: Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 8; Red Hat Enterprise Linux 9.
What this means
In plain English
The libsoup WebSocket frame parser does not correctly enforce the protocol limit for control-frame payloads. A remote, unauthenticated attacker can send an oversized control frame, causing an internal processing crash instead of immediate connection termination. Applications using libsoup WebSockets may become unavailable as a result.
Vulnerable items
- Red Hat Enterprise Linux 10 — Not specified by the vendor
- Red Hat Enterprise Linux 8 — Not specified by the vendor
- Red Hat Enterprise Linux 9 — Not specified by the vendor
Recommended action
The vendor has not specified a fixed release, mitigation, or workaround. Follow the official advisory for remediation updates.
Written by AI strictly from the parsed advisory data above — versions, scores and dates are never AI-generated. The vendor advisory is authoritative.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · medium-confidence parse· fetched 2 hours ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · medium-confidence parse· fetched 2 hours ago·verify at source
Mitigation
The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.
Official advisory · medium-confidence parse· fetched 2 hours ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.