Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

debian логотип

CVE-2025-5399

Опубликовано: 07 июн. 2025
Источник: debian

Описание

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.

Пакеты

ПакетСтатусВерсия исправленияРелизТип
curlfixed8.14.1-1package
curlnot-affectedbookwormpackage
curlnot-affectedbullseyepackage

Примечания

  • https://curl.se/docs/CVE-2025-5399.html

  • Introduced by: https://github.com/curl/curl/commit/3588df9478d7c27046b34cdb510728a26bedabc7 (curl-8_13_0)

  • Fixed by: https://github.com/curl/curl/commit/d1145df24de8f80e6b167fbc4f28b86bcd0c6832 (curl-8_14_1)

Связанные уязвимости

CVSS3: 7.5
ubuntu
12 дней назад

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.

CVSS3: 4.3
redhat
12 дней назад

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.

CVSS3: 7.5
nvd
12 дней назад

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.

CVSS3: 7.5
github
12 дней назад

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.