Bug 2325276 (CVE-2024-52532) - CVE-2024-52532 libsoup: infinite loop while reading websocket data
Summary: CVE-2024-52532 libsoup: infinite loop while reading websocket data
Keywords:
Status: NEW
Alias: CVE-2024-52532
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2325356 2325357
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-11-11 20:01 UTC by OSIDB Bzimport
Modified: 2025-04-11 07:36 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Gitlab GNOME libsoup issues 391 0 None closed Infinite loop while reading websocket data 2024-11-12 12:36:37 UTC
Red Hat Product Errata RHBA-2024:10617 0 None None None 2024-12-02 03:13:49 UTC
Red Hat Product Errata RHBA-2024:9675 0 None None None 2024-11-14 14:05:56 UTC
Red Hat Product Errata RHBA-2024:9822 0 None None None 2024-11-18 01:40:22 UTC
Red Hat Product Errata RHBA-2024:9836 0 None None None 2024-11-18 09:38:40 UTC
Red Hat Product Errata RHBA-2024:9863 0 None None None 2024-11-18 10:44:09 UTC
Red Hat Product Errata RHSA-2024:9559 0 None None None 2024-11-13 15:27:25 UTC
Red Hat Product Errata RHSA-2024:9573 0 None None None 2024-11-13 18:09:56 UTC

Description OSIDB Bzimport 2024-11-11 20:01:28 UTC 
GNOME libsoup before 3.6.1 has an infinite loop, and memory consumption. during the reading of certain patterns of WebSocket data from clients.
Comment 2 errata-xmlrpc 2024-11-13 15:27:24 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2024:9559 https://access.redhat.com/errata/RHSA-2024:9559
Comment 3 errata-xmlrpc 2024-11-13 18:09:55 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2024:9573 https://access.redhat.com/errata/RHSA-2024:9573
Note You need to log in before you can comment on or make changes to this bug.