CVE-2024-7264 — ASN.1 date parser overread
libcurl's ASN1 parser code has the `GTime2str()` function, used for parsing an ASN.1 Generalized Time field. If given an syntactically incorrect field, the parser might end up using -1 for the length of the *time fraction*, leading to a `strlen()` getting performed on a pointer to a heap buffer area that is not (purposely) null terminated. This flaw most likely leads to a crash, but can also lead to heap contents getting returned to the application when [CURLINFO_CERTINFO](https://curl.se/libcurl/c/CURLINFO_CERTINFO.html) is used.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 17.3% (30-day exploitation probability)+15
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Curl Curl, Haxx Libcurl).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Exploitation requires user interaction: tighten email/web filtering and warn affected users.
- EPSS ahead of 97% of scored CVEs: prioritize it in the patch queue.
- Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Curl | Curl |
≥ 7.56.0 and ≤ 7.56.0≥ 7.50.2 and ≤ 7.50.2≥ 7.50.3 and ≤ 7.50.3≥ 7.51.0 and ≤ 7.51.0≥ 7.52.0 and ≤ 7.52.0≥ 7.52.1 and ≤ 7.52.1≥ 7.53.0 and ≤ 7.53.0≥ 7.53.1 and ≤ 7.53.1 and 87 more≥ 7.54.0 and ≤ 7.54.0≥ 7.54.1 and ≤ 7.54.1≥ 7.55.0 and ≤ 7.55.0≥ 7.55.1 and ≤ 7.55.1≥ 7.50.1 and ≤ 7.50.1≥ 7.56.1 and ≤ 7.56.1≥ 7.57.0 and ≤ 7.57.0≥ 7.58.0 and ≤ 7.58.0≥ 7.59.0 and ≤ 7.59.0≥ 7.60.0 and ≤ 7.60.0≥ 7.61.0 and ≤ 7.61.0≥ 7.61.1 and ≤ 7.61.1≥ 7.62.0 and ≤ 7.62.0≥ 7.63.0 and ≤ 7.63.0≥ 7.64.0 and ≤ 7.64.0≥ 7.64.1 and ≤ 7.64.1≥ 7.42.0 and ≤ 7.42.0≥ 7.32.0 and ≤ 7.32.0≥ 7.33.0 and ≤ 7.33.0≥ 7.34.0 and ≤ 7.34.0≥ 7.35.0 and ≤ 7.35.0≥ 7.36.0 and ≤ 7.36.0≥ 7.37.0 and ≤ 7.37.0≥ 7.37.1 and ≤ 7.37.1≥ 7.38.0 and ≤ 7.38.0≥ 7.39.0 and ≤ 7.39.0≥ 7.40.0 and ≤ 7.40.0≥ 7.41.0 and ≤ 7.41.0≥ 8.8.0 and ≤ 8.8.0≥ 7.42.1 and ≤ 7.42.1≥ 7.43.0 and ≤ 7.43.0≥ 7.44.0 and ≤ 7.44.0≥ 7.45.0 and ≤ 7.45.0≥ 7.46.0 and ≤ 7.46.0≥ 7.47.0 and ≤ 7.47.0≥ 7.47.1 and ≤ 7.47.1≥ 7.48.0 and ≤ 7.48.0≥ 7.49.0 and ≤ 7.49.0≥ 7.49.1 and ≤ 7.49.1≥ 7.50.0 and ≤ 7.50.0≥ 8.1.0 and ≤ 8.1.0≥ 7.82.0 and ≤ 7.82.0≥ 7.83.0 and ≤ 7.83.0≥ 7.83.1 and ≤ 7.83.1≥ 7.84.0 and ≤ 7.84.0≥ 7.85.0 and ≤ 7.85.0≥ 7.86.0 and ≤ 7.86.0≥ 7.87.0 and ≤ 7.87.0≥ 7.88.0 and ≤ 7.88.0≥ 7.88.1 and ≤ 7.88.1≥ 8.0.0 and ≤ 8.0.0≥ 8.0.1 and ≤ 8.0.1≥ 7.65.1 and ≤ 7.65.1≥ 8.1.1 and ≤ 8.1.1≥ 8.1.2 and ≤ 8.1.2≥ 8.2.0 and ≤ 8.2.0≥ 8.2.1 and ≤ 8.2.1≥ 8.3.0 and ≤ 8.3.0≥ 8.4.0 and ≤ 8.4.0≥ 8.5.0 and ≤ 8.5.0≥ 8.6.0 and ≤ 8.6.0≥ 8.7.0 and ≤ 8.7.0≥ 8.7.1 and ≤ 8.7.1≥ 8.9.0 and ≤ 8.9.0≥ 7.80.0 and ≤ 7.80.0≥ 7.65.0 and ≤ 7.65.0≥ 7.65.2 and ≤ 7.65.2≥ 7.65.3 and ≤ 7.65.3≥ 7.66.0 and ≤ 7.66.0≥ 7.67.0 and ≤ 7.67.0≥ 7.68.0 and ≤ 7.68.0≥ 7.69.0 and ≤ 7.69.0≥ 7.69.1 and ≤ 7.69.1≥ 7.70.0 and ≤ 7.70.0≥ 7.71.0 and ≤ 7.71.0≥ 7.71.1 and ≤ 7.71.1≥ 7.72.0 and ≤ 7.72.0≥ 7.73.0 and ≤ 7.73.0≥ 7.74.0 and ≤ 7.74.0≥ 7.75.0 and ≤ 7.75.0≥ 7.76.0 and ≤ 7.76.0≥ 7.76.1 and ≤ 7.76.1≥ 7.77.0 and ≤ 7.77.0≥ 7.78.0 and ≤ 7.78.0≥ 7.79.0 and ≤ 7.79.0≥ 7.79.1 and ≤ 7.79.1≥ 7.81.0 and ≤ 7.81.0 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
| Haxx | Libcurl | ≥ 7.32.0 and < 8.9.1 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 6.5 | CVSS 3.1 | Medium | 2.8 | 3.6 | nvd@nist.gov via NIST National Vulnerability Database |
| 6.5 | CVSS 3.1 | Medium | — | — | GitHub, Inc. via GitHub Security Advisories |
| 6.3 | CVSS 3.1 | Medium | 2.8 | 3.4 | 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database |
| 6.3 | CVSS 3.1 | Medium | — | — | CISA-ADP via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · curl/curl
- SSVC assessment updated
- Record published
- Affected products added · haxx/libcurl
- CVSS changed · 6.5
- Source status changed · → Modified
- Record created in this database
- 2024
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 14, 2026 – Oct 14, 2026
References
16 on the record
- curl.se/docs/CVE-2024-7264.html
- curl.se/docs/CVE-2024-7264.json
- cert-portal.siemens.com/productcert/html/ssa-398330.html
- security.netapp.com/advisory/ntap-20240828-0008/
- cert-portal.siemens.com/productcert/html/ssa-355557.html
- security.netapp.com/advisory/ntap-20240828-0008
- cert-portal.siemens.com/productcert/html/ssa-089022.html
- security.netapp.com/advisory/ntap-20241025-0010/
- security.netapp.com/advisory/ntap-20241025-0006/
- hackerone.com/reports/2629968
- www.openwall.com/lists/oss-security/2024/07/31/1
- nvd.nist.gov/vuln/detail/CVE-2024-7264
- security.netapp.com/advisory/ntap-20241025-0006
- github.com/curl/curl/commit/27959ecce75cdb2809c0bdb3286e60e08fadb519
- security.netapp.com/advisory/ntap-20241025-0010
- github.com/advisories/GHSA-97c4-2w4v-c7r8
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-92392 HTTP/2 upload Use-After-Free 1d
- Critical CVE-2026-9079 stale proxy password leak Jul 3, 2026
- High CVE-2026-8932 incomplete mTLS config matching in conn reuse Jul 3, 2026
- High CVE-2026-9080 UAF after pause in socket callback Jul 3, 2026
- High CVE-2026-9545 exposing HTTP/3 early data Jul 3, 2026
- High CVE-2026-9546 sending old referer Jul 3, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2024-7264 is "ASN.1 date parser overread", rated Medium. It affects Curl (Curl); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.5 describes technical severity. EPSS 17.30% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.