A use after free vulnerability exists in curl <7.87.0.

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

• apple macos13.0 and later · before 13.3
• haxx curlbefore 7.87.0
• splunk universal forwarder8.2.0 and later · before 8.2.12
• splunk universal forwarder9.0.0 and later · before 9.0.6
• splunk universal forwarder9.1.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (hackerone). Independent of NVD's CPE analysis and usually ahead of it.

• n/a https://github.com/curl/curl

  • Fixed in curl 7.87.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Other highest-scoring records for the same primary product.

• CVE-2021-22901curl 7.75.0 through 7.76.1 suffers from a use-after-free vulnerability resulting in already freed memory being used when a TLS 1.3 session t
  51Plan
• CVE-2023-38039When curl retrieves an HTTP response, it stores the incoming headers so that they can be accessed later via the libcurl headers API.
  47Plan
• CVE-2024-2398HTTP/2 push headers memory-leak
  45Plan

Published before and after this one in the same product

• ← EarlierCVE-2022-35260Dec 5, 2022 · curl can be told to parse a `.netrc` file for credentials.
  27Monitor
• ← EarlierCVE-2022-43551Dec 23, 2022 · A vulnerability exists in curl <7.87.0 HSTS check that could be bypassed to trick it to keep using HTTP.
  35Monitor
• Later →CVE-2023-23914Feb 23, 2023 · A cleartext transmission of sensitive information vulnerability exists in curl <v7.88.0 that could cause HSTS functionality fail when multip
  36Monitor

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

1free(dev->buf);2/* ... another thread is still running ... */3process(dev->buf);

1lock(&dev->lock);2free(dev->buf);3dev->buf = NULL;4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.