CVE-2023-38039highCWE-770

CVE-2023-38039: high-severity vulnerability in curl

Published · Updated

Follow this CVE+ Monitor curl+ Monitor curl

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

33Vexday Risk Score

No sign of exploitation. No public exploitation artifact known so far.

ssvc Trackcvss 7.5epss 56%
What the vendors declare (VEX)

Official vendor statements in CSAF/VEX format: whether their product is affected, already fixed, or ruled out — and why. These are the vendor's assertions, not Vexday's judgment.

Red HatVEX document ↗
Fixed
2 products (11 components)
Red Hat JBoss Core Services on RHEL 8 · Red Hat JBoss Core Services on RHEL 7 Server
fix ↗
Not affected
6 products (132 components) — because the vulnerable code is not present in the product
Red Hat JBoss Core Services on RHEL 8 · Red Hat JBoss Core Services on RHEL 7 Server · Red Hat Enterprise Linux 9 · Red Hat Enterprise Linux 8 · Red Hat Enterprise Linux 6 · and others 1
When curl retrieves an HTTP response, it stores the incoming headers so that they can be accessed later via the libcurl headers API. However, curl did not have a limit in how many or how large headers it would accept in a response, allowing a malicious server to stream an endless series of headers and eventually cause curl to run out of heap memory.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Affected products
curl · curl
Related CVEs — curl

In the same product, most dangerous first.

CVE-2023-38545HIGHCVE-2023-38545EPSS 78.7%CVE-2019-5436HIGHCVE-2019-5436EPSS 49.7%CVE-2024-2398HIGHHTTP/2 push headers memory-leakEPSS 36.1%CVE-2024-7264MEDIUMASN.1 date parser overreadEPSS 20.2%CVE-2023-38546—CVE-2023-38546EPSS 6.0%CVE-2019-5435—CVE-2019-5435EPSS 5.7%