CVE-2023-28319: A use after free vulnerability exists in curl <v8.1.0 in the way libcurl offers a feature to verify an SSH server's public key using a SHA 2
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 2.4% (FIRST EPSS); higher than 84.6% 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: azl3 tensorflow 2.11.1-1 on Azure Linux 3.0 2.16.1-1; azl3 tensorflow 2.16.1-1 on Azure Linux 3.0 2.16.1-1; cbl2 curl 8.2.1-1 on CBL Mariner 2.0 8.2.1-1.
Low priority for now. Upgrade to azl3 tensorflow 2.11.1-1 on Azure Linux 3.0 2.16.1-1; azl3 tensorflow 2.16.1-1 on Azure Linux 3.0 2.16.1-1; cbl2 curl 8.2.1-1 on CBL Mariner 2.0 8.2.1-1 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
A use after free vulnerability exists in curl <v8.1.0 in the way libcurl offers a feature to verify an SSH server's public key using a SHA 256 hash. When this check fails, libcurl would free the memory for the fingerprint before it returns an error message containing the (now freed) hash. This flaw risks inserting sensitive heap-based data into the error message that might be shown to users or otherwise get leaked and revealed.
- Published
- May 26, 2023
- Updated
- Oct 23, 2026
- EPSS
- 2.4% · 84th percentile
- CWE
- CWE-416
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.4%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.5
- CNA · hackerone
- 7.5
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 |
| netapp | h500s | cpe:2.3:h:netapp:h500s |
| apple | macos | cpe:2.3:o:apple:macos |
| netapp | clustered data ontap | cpe:2.3:a:netapp:clustered_data_ontap |
| netapp | ontap antivirus connector | cpe:2.3:a:netapp:ontap_antivirus_connector |
| netapp | h300s firmware | cpe:2.3:o:netapp:h300s_firmware |
| netapp | h300s | cpe:2.3:h:netapp:h300s |
| netapp | h500s firmware | cpe:2.3:o:netapp:h500s_firmware |
| netapp | h700s firmware | cpe:2.3:o:netapp:h700s_firmware |
| netapp | h700s | cpe:2.3:h:netapp:h700s |
| netapp | h410s firmware | cpe:2.3:o:netapp:h410s_firmware |
| netapp | h410s | cpe:2.3:h:netapp:h410s |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- apple macos11.0 and later · before 11.7.9
- apple macos12.0 and later · before 12.6.8
- apple macos13.0 and later · before 13.5
- haxx curlbefore 8.1.0
- netapp clustered data ontapall versions
- netapp h300s firmwareall versions
- netapp h410s firmwareall versions
- netapp h500s firmwareall versions
- netapp h700s firmwareall versions
- netapp ontap antivirus connectorall versions
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 8.1.0affected
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 | before 8.1.0-r0 | 8.1.0-r0 |
| Debian:12 | curl | before 7.88.1-10 | 7.88.1-10 |
| openSUSE:Leap Micro 5.3 | curl | before 8.0.1-150400.5.23.1 | 8.0.1-150400.5.23.1 |
| openSUSE:Tumbleweed | curl | before 8.1.0-1.1 | 8.1.0-1.1 |
| Red Hat:jboss_core_services:1::el7 | jbcs-httpd24-apr | before 0:1.7.0-8.el7jbcs | 0:1.7.0-8.el7jbcs |
| Red Hat:jboss_core_services:1::el7 | jbcs-httpd24-apr-debuginfo | before 0:1.7.0-8.el7jbcs | 0:1.7.0-8.el7jbcs |
| Red Hat:jboss_core_services:1::el7 | jbcs-httpd24-apr-devel | before 0:1.7.0-8.el7jbcs | 0:1.7.0-8.el7jbcs |
| Red Hat:jboss_core_services:1::el7 | jbcs-httpd24-curl | before 0:8.2.1-1.el7jbcs | 0:8.2.1-1.el7jbcs |
| Red Hat:jboss_core_services:1::el7 | jbcs-httpd24-curl-debuginfo | before 0:8.2.1-1.el7jbcs | 0:8.2.1-1.el7jbcs |
| Red Hat:jboss_core_services:1::el7 | jbcs-httpd24-httpd | before 0:2.4.57-5.el7jbcs | 0:2.4.57-5.el7jbcs |
| Red Hat:jboss_core_services:1::el7 | jbcs-httpd24-httpd-debuginfo | before 0:2.4.57-5.el7jbcs | 0:2.4.57-5.el7jbcs |
| Red Hat:jboss_core_services:1::el7 | jbcs-httpd24-httpd-devel | before 0:2.4.57-5.el7jbcs | 0:2.4.57-5.el7jbcs |
| Red Hat:jboss_core_services:1::el7 | jbcs-httpd24-httpd-manual | before 0:2.4.57-5.el7jbcs | 0:2.4.57-5.el7jbcs |
| Red Hat:jboss_core_services:1::el7 | jbcs-httpd24-httpd-selinux | before 0:2.4.57-5.el7jbcs | 0:2.4.57-5.el7jbcs |
| Red Hat:jboss_core_services:1::el7 | jbcs-httpd24-httpd-tools | before 0:2.4.57-5.el7jbcs | 0:2.4.57-5.el7jbcs |
| Red Hat:jboss_core_services:1::el7 | jbcs-httpd24-libcurl | before 0:8.2.1-1.el7jbcs | 0:8.2.1-1.el7jbcs |
| Red Hat:jboss_core_services:1::el7 | jbcs-httpd24-libcurl-devel | before 0:8.2.1-1.el7jbcs | 0:8.2.1-1.el7jbcs |
| Red Hat:jboss_core_services:1::el7 | jbcs-httpd24-mod_ldap | before 0:2.4.57-5.el7jbcs | 0:2.4.57-5.el7jbcs |
| Red Hat:jboss_core_services:1::el7 | jbcs-httpd24-mod_proxy_html | before 1:2.4.57-5.el7jbcs | 1:2.4.57-5.el7jbcs |
| Red Hat:jboss_core_services:1::el7 | jbcs-httpd24-mod_security | before 0:2.9.3-29.el7jbcs | 0:2.9.3-29.el7jbcs |
| Red Hat:jboss_core_services:1::el7 | jbcs-httpd24-mod_security-debuginfo | before 0:2.9.3-29.el7jbcs | 0:2.9.3-29.el7jbcs |
| Red Hat:jboss_core_services:1::el7 | jbcs-httpd24-mod_session | before 0:2.4.57-5.el7jbcs | 0:2.4.57-5.el7jbcs |
| Red Hat:jboss_core_services:1::el7 | jbcs-httpd24-mod_ssl | before 1:2.4.57-5.el7jbcs | 1:2.4.57-5.el7jbcs |
| Red Hat:jboss_core_services:1::el8 | jbcs-httpd24-apr | before 0:1.7.0-8.el8jbcs | 0:1.7.0-8.el8jbcs |
+26
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 t51Plan
- 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-leak45Plan
Published before and after this one in the same product
- ← EarlierCVE-2023-27533Mar 30, 2023 · A vulnerability in input validation exists in curl <8.0 during communication using the TELNET protocol may allow an attacker to pass on mali36Monitor
- ← EarlierCVE-2023-27534Mar 30, 2023 · A path traversal vulnerability exists in curl <8.0.0 SFTP implementation causes the tilde (~) character to be wrongly replaced when used as 36Monitor
- Later →CVE-2023-28320May 26, 2023 · A denial of service vulnerability exists in curl <v8.1.0 in the way libcurl provides several different backends for resolving host names, se24Monitor
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 |
|---|---|---|
| azl3 tensorflow 2.11.1-1 on Azure Linux 3.0 | 2.16.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 tensorflow 2.16.1-1 on Azure Linux 3.0 | 2.16.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 curl 8.2.1-1 on CBL Mariner 2.0 | 8.2.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 mysql 8.0.34-1 on CBL Mariner 2.0 | 8.0.34-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 rust 1.72.0-2 on CBL Mariner 2.0 | 1.72.0-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| alpine:curl | 8.1.0-r0 · Alpine:v3.15 | Package registry (OSV) |
| debian:curl | 7.88.1-10 · Debian:12 | Package registry (OSV) |
| opensuse:curl | 8.0.1-150400.5.23.1 · openSUSE:Leap Micro 5.3 | Package registry (OSV) |
| red hat:jbcs-httpd24-apr | 0:1.7.0-8.el7jbcs · Red Hat:jboss_core_services:1::el7 | Package registry (OSV) |
| red hat:jbcs-httpd24-apr-debuginfo | 0:1.7.0-8.el7jbcs · Red Hat:jboss_core_services:1::el7 | Package registry (OSV) |
| red hat:jbcs-httpd24-apr-devel | 0:1.7.0-8.el7jbcs · Red Hat:jboss_core_services:1::el7 | Package registry (OSV) |
| red hat:jbcs-httpd24-httpd | 0:2.4.57-5.el7jbcs · Red Hat:jboss_core_services:1::el7 | Package registry (OSV) |
| red hat:jbcs-httpd24-httpd-debuginfo | 0:2.4.57-5.el7jbcs · Red Hat:jboss_core_services:1::el7 | Package registry (OSV) |
| red hat:jbcs-httpd24-httpd-devel | 0:2.4.57-5.el7jbcs · Red Hat:jboss_core_services:1::el7 | Package registry (OSV) |
| red hat:jbcs-httpd24-httpd-manual | 0:2.4.57-5.el7jbcs · Red Hat:jboss_core_services:1::el7 | Package registry (OSV) |
| red hat:jbcs-httpd24-httpd-selinux | 0:2.4.57-5.el7jbcs · Red Hat:jboss_core_services:1::el7 | Package registry (OSV) |
| red hat:jbcs-httpd24-httpd-tools | 0:2.4.57-5.el7jbcs · Red Hat:jboss_core_services:1::el7 | Package registry (OSV) |
| red hat:jbcs-httpd24-mod_ldap | 0:2.4.57-5.el7jbcs · Red Hat:jboss_core_services:1::el7 | Package registry (OSV) |
| red hat:jbcs-httpd24-mod_proxy_html | 1:2.4.57-5.el7jbcs · Red Hat:jboss_core_services:1::el7 | Package registry (OSV) |
| red hat:jbcs-httpd24-mod_session | 0:2.4.57-5.el7jbcs · Red Hat:jboss_core_services:1::el7 | Package registry (OSV) |
| suse:curl | 8.0.1-150400.5.23.1 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
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.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
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
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-primary
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.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&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.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.