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.
The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop.
Link | Tags |
---|---|
https://curl.se/docs/CVE-2025-5399.json | vendor advisory |
https://curl.se/docs/CVE-2025-5399.html | vendor advisory |
https://hackerone.com/reports/3168039 | third party advisory issue tracking exploit |
http://www.openwall.com/lists/oss-security/2025/06/04/2 | mailing list third party advisory |