Описание
A flaw was found in libsoup. When reassembling fragmented WebSocket messages into a GByteArray, libsoup did not adequately cap total message size against the limits of the underlying buffer type. A remote peer could send fragments that caused size truncation while the implementation still used the full length, leading to heap corruption or a crash.
A flaw was found in libsoup. When reassembling fragmented WebSocket messages into a GByteArray, libsoup did not adequately cap total message size against the limits of the underlying buffer type. A remote peer could send fragments that caused size truncation while the implementation still used the full length, leading to heap corruption or a crash.
Ссылки
- https://nvd.nist.gov/vuln/detail/CVE-2026-102557
- https://access.redhat.com/errata/RHSA-2026:83384
- https://access.redhat.com/errata/RHSA-2026:83618
- https://access.redhat.com/errata/RHSA-2026:84586
- https://access.redhat.com/errata/RHSA-2026:92347
- https://access.redhat.com/errata/RHSA-2026:93445
- https://access.redhat.com/errata/RHSA-2026:93446
- https://access.redhat.com/errata/RHSA-2026:93447
- https://access.redhat.com/errata/RHSA-2026:93465
- https://access.redhat.com/errata/RHSA-2026:93466
- https://access.redhat.com/errata/RHSA-2026:93583
- https://access.redhat.com/errata/RHSA-2026:93716
- https://access.redhat.com/security/cve/CVE-2026-102557
- https://bugzilla.redhat.com/show_bug.cgi?id=2543231
Связанные уязвимости
A flaw was found in libsoup. When reassembling fragmented WebSocket messages into a GByteArray, libsoup did not adequately cap total message size against the limits of the underlying buffer type. A remote peer could send fragments that caused size truncation while the implementation still used the full length, leading to heap corruption or a crash.
A flaw was found in libsoup. When reassembling fragmented WebSocket messages into a GByteArray, libsoup did not adequately cap total message size against the limits of the underlying buffer type. A remote peer could send fragments that caused size truncation while the implementation still used the full length, leading to heap corruption or a crash.
A flaw was found in libsoup. When reassembling fragmented WebSocket messages into a GByteArray, libsoup did not adequately cap total message size against the limits of the underlying buffer type. A remote peer could send fragments that caused size truncation while the implementation still used the full length, leading to heap corruption or a crash.
Libsoup: libsoup: heap buffer overflow during websocket message reassembly
A flaw was found in libsoup. When reassembling fragmented WebSocket me ...