Bug 2370920 (CVE-2025-5399)

Summary:	CVE-2025-5399 curl: libcurl: WebSocket endless loop
Product:	[Other] Security Response	Reporter:	OSIDB Bzimport <bzimport>
Component:	vulnerability	Assignee:	Product Security DevOps Team <prodsec-dev>
Status:	NEW ---	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	adudiak, crizzo, csutherl, dbosanac, dfreiber, drow, jburrell, jclere, jmitchel, jreimann, jtanner, kshier, mdessi, mrizzi, omaciel, pcattana, pjindal, plodge, stcannon, szappis, vchlup, vkumar, yguenane, ZaneHeller1980
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:	A flaw was found in libcurl's WebSocket handling. This vulnerability allows a malicious server to cause an applicaiton level denial of service (DoS) by triggering an infinite busy-loop, effectively trapping the application thread, via a specially crafted WebSocket packet when "auto-pong" is enabled.	Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2381703, 2381710
Bug Blocks:

Description OSIDB Bzimport 2025-06-07 08:01:06 UTC

Due to a mistake in libcurl's WebSocket code, a malicious server can send a
particularly crafted packet which makes libcurl get trapped in an endless
busy-loop.

There is no other way for the application to escape or exit this loop other
than killing the thread/process.

This might be used to DoS libcurl-using application.

Comment 3 icholasogahn 2025-06-17 07:05:43 UTC

When the flow of the web always tries to invade the device in a path that can be clicked wrong. How to exploit the above measure? https://unoonlinefree.io/

Comment 4 errata-xmlrpc 2025-09-11 14:37:02 UTC

This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2025:15699 https://access.redhat.com/errata/RHSA-2025:15699

Comment 5 errata-xmlrpc 2025-09-17 08:04:17 UTC

This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2025:16046 https://access.redhat.com/errata/RHSA-2025:16046