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.
References
Configurations
No configuration.
History
09 Jun 2025, 14:15
Type | Values Removed | Values Added |
---|---|---|
Summary |
|
|
CVSS |
v2 : v3 : |
v2 : unknown
v3 : 7.5 |
07 Jun 2025, 08:15
Type | Values Removed | Values Added |
---|---|---|
New CVE |
Information
Published : 2025-06-07 08:15
Updated : 2025-06-09 14:15
NVD link : CVE-2025-5399
Mitre link : CVE-2025-5399
CVE.ORG link : CVE-2025-5399
JSON object : View
Products Affected
No product.
CWE
No CWE.