CVE-2022-30115: Using its HSTS support, curl can be instructed to use HTTPS directly insteadof using an insecure clear-text HTTP step even when HTTP is prov
Noroxi assessment
Priority: Monitor (action score 17/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: 1.3% (FIRST EPSS); higher than 71.7% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. 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 (Alpine:v3.16) 7.83.1-r0; curl (Debian:12) 7.83.1-1; curl (openSUSE:Tumbleweed) 7.83.1-1.1.
Low priority for now. Upgrade to curl (Alpine:v3.16) 7.83.1-r0; curl (Debian:12) 7.83.1-1; curl (openSUSE:Tumbleweed) 7.83.1-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
Using its HSTS support, curl can be instructed to use HTTPS directly insteadof using an insecure clear-text HTTP step even when HTTP is provided in theURL. This mechanism could be bypassed if the host name in the given URL used atrailing dot while not using one when it built the HSTS cache. Or the otherway around - by having the trailing dot in the HSTS cache and *not* using thetrailing dot in the URL.
- Published
- Jun 2, 2022
- Updated
- Oct 14, 2026
- EPSS
- 1.3% · 71th percentile
- CWE
- CWE-325
Report tools
Action score
17
Monitor
Low priority for now.
- CVSS
- 17 / 40 · 4.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.3%
CISA SSVC decision
- Exploitation
- none
- 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
- 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 | hci bootstrap os | cpe:2.3:o:netapp:hci_bootstrap_os |
| netapp | hci compute node | cpe:2.3:h:netapp:hci_compute_node |
| netapp | clustered data ontap | cpe:2.3:a:netapp:clustered_data_ontap |
| netapp | solidfire, enterprise sds & hci storage node | cpe:2.3:a:netapp:solidfire,_enterprise_sds_&_hci_storage_node |
| netapp | solidfire & hci management node | cpe:2.3:a:netapp:solidfire_&_hci_management_node |
| 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 | h500s | cpe:2.3:h:netapp:h500s |
| netapp | h700s firmware | cpe:2.3:o:netapp:h700s_firmware |
| netapp | h700s | cpe:2.3:h:netapp:h700s |
and 3 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- haxx curl7.82.0 and later · before 7.83.1
- netapp clustered data ontapall versions
- netapp h300s firmwareall versions
- netapp h410s firmwareall versions
- netapp h500s firmwareall versions
- netapp h700s firmwareall versions
- netapp hci bootstrap osall versions
- netapp solidfire & hci management nodeall versions
- netapp solidfire, enterprise sds & hci storage nodeall versions
- 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 7.83.1affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.16 | curl | from 7.82.0 · before 7.83.1-r0 | 7.83.1-r0 |
| Debian:12 | curl | before 7.83.1-1 | 7.83.1-1 |
| openSUSE:Tumbleweed | curl | before 7.83.1-1.1 | 7.83.1-1.1 |
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-2022-27781Jun 2, 2022 · libcurl provides the `CURLOPT_CERTINFO` option to allow applications torequest details to be returned about a server's certificate chain.Due31Monitor
- ← EarlierCVE-2022-27782Jun 2, 2022 · libcurl would reuse a previously created connection even when a TLS or SSHrelated option had been changed that should have prohibited reuse.31Monitor
- Later →CVE-2022-32205Jul 7, 2022 · A malicious server can serve excessive amounts of `Set-Cookie:` headers in a HTTP response to curl and curl < 7.84.0 stores all of them.26Monitor
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 |
|---|---|---|
| alpine:curl | 7.83.1-r0 · Alpine:v3.16 | Package registry (OSV) |
| debian:curl | 7.83.1-1 · Debian:12 | Package registry (OSV) |
| opensuse:curl | 7.83.1-1.1 · openSUSE:Tumbleweed | 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.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-325 · Missing Cryptographic StepCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
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)
ATT&CK techniques
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.