CVE-2023-38039: When curl retrieves an HTTP response, it stores the incoming headers so that they can be accessed later via the libcurl headers API.
Noroxi assessment
Priority: Plan (action score 47/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 56.2% (FIRST EPSS); higher than 99% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: curl curl 8.3.0.
Add it to your regular patch cycle. Upgrade to curl curl 8.3.0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 15, 2023
- Updated
- Jun 17, 2026
- EPSS
- 56.2% · 99th percentile
- CWE
- CWE-770
Report tools
Action score
47
Add it to your regular patch cycle.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 17 / 30 · 56.2%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| haxx | curl | cpe:2.3:a:haxx:curl |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
| microsoft | windows 10 1809 | cpe:2.3:o:microsoft:windows_10_1809 |
| microsoft | windows 10 21h2 | cpe:2.3:o:microsoft:windows_10_21h2 |
| microsoft | windows 10 22h2 | cpe:2.3:o:microsoft:windows_10_22h2 |
| microsoft | windows 11 21h2 | cpe:2.3:o:microsoft:windows_11_21h2 |
| microsoft | windows 11 22h2 | cpe:2.3:o:microsoft:windows_11_22h2 |
| microsoft | windows 11 23h2 | cpe:2.3:o:microsoft:windows_11_23h2 |
| microsoft | windows server 2019 | cpe:2.3:o:microsoft:windows_server_2019 |
| microsoft | windows server 2022 | cpe:2.3:o:microsoft:windows_server_2022 |
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.
curl curl
- 8.3.0 and later · before 8.3.0affected · semver
- 7.84.0 and later · before 7.84.0not affected · semver
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- microsoft windows server 2019before 10.0.17763.5122
- microsoft windows server 2022before 10.0.20348.2113
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.15 | curl | from 7.84.0 · before 8.3.0-r0 | 8.3.0-r0 |
| Debian:12 | curl | before 7.88.1-10+deb12u3 | 7.88.1-10+deb12u3 |
| Debian:13 | curl | before 8.3.0-1 | 8.3.0-1 |
| openSUSE:Leap 15.4 | curl | before 8.0.1-150400.5.29.1 | 8.0.1-150400.5.29.1 |
| openSUSE:Tumbleweed | curl | before 8.3.0-1.1 | 8.3.0-1.1 |
| Red Hat:jboss_core_services:1::el7 | jbcs-httpd24-curl | before 0:8.4.0-2.el7jbcs | 0:8.4.0-2.el7jbcs |
| Red Hat:jboss_core_services:1::el7 | jbcs-httpd24-curl-debuginfo | before 0:8.4.0-2.el7jbcs | 0:8.4.0-2.el7jbcs |
| Red Hat:jboss_core_services:1::el7 | jbcs-httpd24-libcurl | before 0:8.4.0-2.el7jbcs | 0:8.4.0-2.el7jbcs |
| Red Hat:jboss_core_services:1::el7 | jbcs-httpd24-libcurl-devel | before 0:8.4.0-2.el7jbcs | 0:8.4.0-2.el7jbcs |
| Red Hat:jboss_core_services:1::el7 | jbcs-httpd24-mod_http2 | before 0:1.15.19-32.el7jbcs | 0:1.15.19-32.el7jbcs |
| Red Hat:jboss_core_services:1::el7 | jbcs-httpd24-mod_http2-debuginfo | before 0:1.15.19-32.el7jbcs | 0:1.15.19-32.el7jbcs |
| Red Hat:jboss_core_services:1::el7 | jbcs-httpd24-mod_jk | before 0:1.2.49-1.redhat_1.el7jbcs | 0:1.2.49-1.redhat_1.el7jbcs |
| Red Hat:jboss_core_services:1::el7 | jbcs-httpd24-mod_jk-ap24 | before 0:1.2.49-1.redhat_1.el7jbcs | 0:1.2.49-1.redhat_1.el7jbcs |
| Red Hat:jboss_core_services:1::el7 | jbcs-httpd24-mod_jk-debuginfo | before 0:1.2.49-1.redhat_1.el7jbcs | 0:1.2.49-1.redhat_1.el7jbcs |
| Red Hat:jboss_core_services:1::el7 | jbcs-httpd24-openssl | before 1:1.1.1k-16.el7jbcs | 1:1.1.1k-16.el7jbcs |
| Red Hat:jboss_core_services:1::el7 | jbcs-httpd24-openssl-debuginfo | before 1:1.1.1k-16.el7jbcs | 1:1.1.1k-16.el7jbcs |
| Red Hat:jboss_core_services:1::el7 | jbcs-httpd24-openssl-devel | before 1:1.1.1k-16.el7jbcs | 1:1.1.1k-16.el7jbcs |
| Red Hat:jboss_core_services:1::el7 | jbcs-httpd24-openssl-libs | before 1:1.1.1k-16.el7jbcs | 1:1.1.1k-16.el7jbcs |
| Red Hat:jboss_core_services:1::el7 | jbcs-httpd24-openssl-perl | before 1:1.1.1k-16.el7jbcs | 1:1.1.1k-16.el7jbcs |
| Red Hat:jboss_core_services:1::el7 | jbcs-httpd24-openssl-static | before 1:1.1.1k-16.el7jbcs | 1:1.1.1k-16.el7jbcs |
| Red Hat:jboss_core_services:1::el8 | jbcs-httpd24-curl | before 0:8.4.0-2.el8jbcs | 0:8.4.0-2.el8jbcs |
| Red Hat:jboss_core_services:1::el8 | jbcs-httpd24-curl-debuginfo | before 0:8.4.0-2.el8jbcs | 0:8.4.0-2.el8jbcs |
| Red Hat:jboss_core_services:1::el8 | jbcs-httpd24-libcurl | before 0:8.4.0-2.el8jbcs | 0:8.4.0-2.el8jbcs |
| Red Hat:jboss_core_services:1::el8 | jbcs-httpd24-libcurl-debuginfo | before 0:8.4.0-2.el8jbcs | 0:8.4.0-2.el8jbcs |
+15
Same product
haxx: all recordsOther 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…51Plan
- CVE-2024-2398HTTP/2 push headers memory-leak45Plan
- CVE-2019-5482Heap buffer overflow in the TFTP protocol handler in cURL 7.19.4 to 7.65.3.44Plan
Published before and after this one in the same product
- ← EarlierCVE-2023-28322May 26, 2023 · An information disclosure vulnerability exists in curl <v8.1.0 when doing HTTP(S) transfers, libcurl might erroneously use the read…15Monitor
- ← EarlierCVE-2020-19909Aug 22, 2023 · Integer overflow vulnerability in tool_operate.c in curl 7.65.2 via a large value as the retry delay.13Monitor
- Later →CVE-2023-46218Dec 6, 2023 · This flaw allows a malicious HTTP server to set "super cookies" in curl that
are then passed back to more origins than what is otherwise…27Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| curl curl | 8.3.0 | Vendor (CNA) |
| alpine:curl | 8.3.0-r0 · Alpine:v3.15 | Package registry (OSV) |
| debian:curl | 7.88.1-10+deb12u3 · Debian:12 | Package registry (OSV) |
| opensuse:curl | 8.0.1-150400.5.29.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| red hat:jbcs-httpd24-curl | 0:8.4.0-2.el7jbcs · Red Hat:jboss_core_services:1::el7 | Package registry (OSV) |
| red hat:jbcs-httpd24-curl-debuginfo | 0:8.4.0-2.el7jbcs · Red Hat:jboss_core_services:1::el7 | Package registry (OSV) |
| red hat:jbcs-httpd24-libcurl | 0:8.4.0-2.el7jbcs · Red Hat:jboss_core_services:1::el7 | Package registry (OSV) |
| red hat:jbcs-httpd24-libcurl-debuginfo | 0:8.4.0-2.el8jbcs · Red Hat:jboss_core_services:1::el8 | Package registry (OSV) |
| red hat:jbcs-httpd24-libcurl-devel | 0:8.4.0-2.el7jbcs · Red Hat:jboss_core_services:1::el7 | Package registry (OSV) |
| red hat:jbcs-httpd24-openssl | 1:1.1.1k-16.el7jbcs · Red Hat:jboss_core_services:1::el7 | Package registry (OSV) |
| red hat:jbcs-httpd24-openssl-debuginfo | 1:1.1.1k-16.el7jbcs · Red Hat:jboss_core_services:1::el7 | Package registry (OSV) |
| red hat:jbcs-httpd24-openssl-devel | 1:1.1.1k-16.el7jbcs · Red Hat:jboss_core_services:1::el7 | Package registry (OSV) |
| red hat:jbcs-httpd24-openssl-libs | 1:1.1.1k-16.el7jbcs · Red Hat:jboss_core_services:1::el7 | Package registry (OSV) |
| red hat:jbcs-httpd24-openssl-libs-debuginfo | 1:1.1.1k-16.el8jbcs · Red Hat:jboss_core_services:1::el8 | Package registry (OSV) |
| red hat:jbcs-httpd24-openssl-perl | 1:1.1.1k-16.el7jbcs · Red Hat:jboss_core_services:1::el7 | Package registry (OSV) |
| red hat:jbcs-httpd24-openssl-static | 1:1.1.1k-16.el7jbcs · Red Hat:jboss_core_services:1::el7 | Package registry (OSV) |
| suse:curl | 8.0.1-11.71.1 · SUSE:Linux Enterprise Software Development Kit 12 SP5 | Package registry (OSV) |
| suse:curl | 8.0.1-150400.5.29.1 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:0 | 2024-05-20 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+248 d
- TodayNov 14, 2026+1156 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-770 · Allocation of Resources Without Limits or ThrottlingCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- FloodingCAPEC-125likelihood: High · Medium
- Excessive AllocationCAPEC-130likelihood: Medium · Medium
- XML Ping of the DeathCAPEC-147likelihood: Low · Medium
- Exponential Data ExpansionCAPEC-197likelihood: High · Medium
- Serialized Data Parameter BlowupCAPEC-229likelihood: High · High
- Serialized Data with Nested PayloadsCAPEC-230likelihood: Medium · High
- Oversized Serialized Data PayloadsCAPEC-231likelihood: Medium · High
- HTTP DoSCAPEC-469Low
ATT&CK techniques
- Network Denial of Service:Direct Network FloodT1498.001
- Network Denial of Service:Reflection AmplificationT1498.002
- Endpoint Denial of ServiceT1499
- Endpoint Denial of Service: OS Exhaustion FloodT1499.001
- Endpoint Denial of Service:Service Exhaustion FloodT1499.002
- Endpoint Denial of Service:Application Exhaustion FloodT1499.003
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (13 more)Show less
- seclists.org/fulldisclosure/2024/Jan/34
- seclists.org/fulldisclosure/2024/Jan/37
- seclists.org/fulldisclosure/2024/Jan/38
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/5DCZMYODALBLVOXVJEN2LF2MLANEYL4F/
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/M6KGKB2JNZVT276JYSKI6FV2VFJUGDOJ/
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TEAWTYHC3RT6ZRS5OZRHLAIENVN6CCIS/
- security.gentoo.org/glsa/202310-12
- security.netapp.com/advisory/ntap-20231013-0005/
- support.apple.com/kb/HT214036
- support.apple.com/kb/HT214057
- support.apple.com/kb/HT214058
- support.apple.com/kb/HT214063
- www.insyde.com/security-pledge/SA-2023064
Vendor advisories and official records. Exploit/PoC links are deliberately left out.