Описание
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 severity of this vulnerability is rated Moderate, as it does not impact system availability. The effects are confined to the application layer, without compromising the underlying system stability.
Меры по смягчению последствий
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Затронутые пакеты
Платформа | Пакет | Состояние | Рекомендация | Релиз |
---|---|---|---|---|
Confidential Compute Attestation | confidential-compute-attestation-tech-preview/trustee-rhel9 | Not affected | ||
Red Hat Enterprise Linux 10 | curl | Not affected | ||
Red Hat Enterprise Linux 10 | rust | Not affected | ||
Red Hat Enterprise Linux 10 | snphost | Not affected | ||
Red Hat Enterprise Linux 10 | trustee-guest-components | Not affected | ||
Red Hat Enterprise Linux 6 | curl | Not affected | ||
Red Hat Enterprise Linux 7 | curl | Not affected | ||
Red Hat Enterprise Linux 8 | curl | Not affected | ||
Red Hat Enterprise Linux 9 | curl | Not affected | ||
Red Hat Enterprise Linux 9 | rust | Not affected |
Показывать по
Дополнительная информация
Статус:
4.3 Medium
CVSS3
Связанные уязвимости
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.
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.
Due to a mistake in libcurl's WebSocket code, a malicious server can s ...
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.
4.3 Medium
CVSS3