Cyber Resilience

CVE-2023-38039

DoS in Fedoraproject Fedora 37 … 39

Public PoCHigh EPSSDoS
Published
15 September 2023
Modified
02 December 2025
Patch / advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.62 99.1th percentile
Risk Priority 81 floored blend · peak EPSS

Summary

CVE-2023-38039 is a high-severity Allocation of Resources Without Limits or Throttling (CWE-770) vulnerability in Fedoraproject Fedora. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Network Denial of Service (T1498); ranked in the top 0.9% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2023-38039 affects curl and its libcurl component. When processing an HTTP response, curl stores incoming headers for later access via the headers API but imposes no limit on the number or total size of those headers. A remote server can therefore send an unbounded stream of headers, exhausting heap memory and triggering a denial-of-service condition. The flaw is tracked as CWE-770 and carries a CVSS 3.1 score of 7.5.

An attacker who controls or can influence an HTTP server reachable by a curl client can exploit the issue simply by returning an endless sequence of headers in a response. No authentication or user interaction is required, and the attack results in heap-memory exhaustion on the client, terminating the transfer or crashing the application.

The EPSS score has remained stable near 0.15 with no material post-disclosure climb from a low baseline.

EU & UK References

Vulnerability Data

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…

more

in a response, allowing a malicious server to stream an endless series of headers and eventually cause curl to run out of heap memory.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1498 Network Denial of Service Impact
Adversaries may perform Network Denial of Service (DoS) attacks to degrade or block the availability of targeted resources to users.
T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
T1499.003 Application Exhaustion Flood Impact
Adversaries may target resource intensive features of applications to cause a denial of service (DoS), denying availability to those applications.
T1498.001 Direct Network Flood Impact
Adversaries may attempt to cause a denial of service (DoS) by directly sending a high-volume of network traffic to a target.
T1498.002 Reflection Amplification Impact
Adversaries may attempt to cause a denial of service (DoS) by reflecting a high-volume of network traffic to a target.
T1499.001 OS Exhaustion Flood Impact
Adversaries may launch a denial of service (DoS) attack targeting an endpoint's operating system (OS).
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-50172Same product: Microsoft Windows 10 1809
CVE-2026-54113Same product: Microsoft Windows 10 1809
CVE-2026-49787Same product: Microsoft Windows 10 1809
CVE-2026-49788Same product: Microsoft Windows 10 1809
CVE-2025-29954Same product: Microsoft Windows 10 1809
CVE-2026-47302Same product: Microsoft Windows 10 1809
CVE-2026-50525Same product: Microsoft Windows 10 1809
CVE-2026-50648Same product: Microsoft Windows 10 1809
CVE-2024-43567Same product: Microsoft Windows Server 2019
CVE-2025-29957Same product: Microsoft Windows 10 1809

Affected Assets

haxx
curl
7.84.0 — 8.3.0
fedoraproject
fedora
37, 38, 39
microsoft
windows 10 1809
≤ 10.0.17763.5122
microsoft
windows 10 21h2
≤ 10.0.19044.3693
microsoft
windows 10 22h2
≤ 10.0.19045.3693
microsoft
windows 11 21h2
≤ 10.0.22000.2600
microsoft
windows 11 22h2
≤ 10.0.22621.2715
microsoft
windows 11 23h2
≤ 10.0.22631.2715
microsoft
windows server 2019
≤ 10.0.17763.5122
microsoft
windows server 2022
≤ 10.0.20348.2113

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 5 hardening rules · 3 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V15.4.4

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-770

This control implements explicit throttling on session allocation, addressing the weakness of allocating resources without limits.

addresses: CWE-770

Plan testing exercises resource allocation limits and throttling during simulated failures, directly addressing weaknesses that allow unbounded resource use.

addresses: CWE-770

Contingency plan updates ensure recovery strategies address unbounded resource allocation, making it harder for attackers to exploit lack of throttling to cause prolonged outages.

addresses: CWE-770

Provides continuity when unbounded resource allocation at the primary site leads to exhaustion and downtime.

addresses: CWE-770

Alternate services allow operations to continue when primary allocation of resources lacks limits or throttling.

addresses: CWE-770

Explicit planning of security-related actions requires defining limits, windows, and resource allocations, making allocation without throttling far less likely.

addresses: CWE-770

Measures of performance include tracking allocation behavior and throttling effectiveness, reducing the window for resource exhaustion attacks.

addresses: CWE-770

Imposes an inactivity-based limit on network resource allocation, throttling the number of concurrently held connections.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.IR-04 mostly match
degrades

Monitoring capacity and taking action to maintain availability directly reduces unchecked resource allocation.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Baseline comparison of CPU, memory and bandwidth usage helps surface uncontrolled resource allocations before they cause service degradation.

prevents

Capacity projections and elasticity measures ensure that allocation requests are bounded and can be throttled, reducing the window in which an attacker can force unbounded resource reservations.

mitigates

Defining retention periods and deletion schedules for backup copies prevents indefinite accumulation of data on storage media without corresponding resource-management controls.

mitigates

Architectural redundancy and automatic failover limit the impact of an attacker who forces excessive allocations, because spare capacity can absorb the load until the primary instance recovers.

none

Documented incident response procedures that include activation of continuity plans and controlled recovery help ensure that resource consumption triggered by an incident is bounded and managed rather than left unbounded.

mitigates

Mandating tested continuity procedures that preserve or replace resource-limiting controls prevents an attacker from exploiting the absence of throttling mechanisms during an outage.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (2 rules)
  • V-248552 OL 8 must be configured so that all network connections associated with SSH traffic terminate after becoming unresponsive. prevents CWE-770
  • V-248553 OL 8 must be configured so that all network connections associated with SSH traffic are terminated after 10 minutes of becoming unresponsive. prevents CWE-770
Oracle Linux 9 (2 rules)
  • V-271710 OL 9 must be configured so that all network connections associated with SSH traffic are terminated after 10 minutes of becoming unresponsive. prevents CWE-770
  • V-271709 OL 9 must be configured so that all network connections associated with SSH traffic terminate after becoming unresponsive. prevents CWE-770
RHEL 8 (1 rule)
  • V-230244 RHEL 8 must be configured so that all network connections associated with SSH traffic terminate after becoming unresponsive. prevents CWE-770

References