CVE-2022-22576: An improper authentication vulnerability exists in curl 7.33.0 to and including 7.82.0 which might allow reuse OAUTH2-authenticated connecti
Noroxi assessment
Priority: Monitor (action score 33/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.5% (FIRST EPSS); higher than 84.8% 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.
- Fixed version: curl (AlmaLinux:8) 7.61.1-22.el8_6.3; libcurl (AlmaLinux:8) 7.61.1-22.el8_6.3; libcurl-devel (AlmaLinux:8) 7.61.1-22.el8_6.3.
- Mentioned 5 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to curl (AlmaLinux:8) 7.61.1-22.el8_6.3; libcurl (AlmaLinux:8) 7.61.1-22.el8_6.3; libcurl-devel (AlmaLinux:8) 7.61.1-22.el8_6.3 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
An improper authentication vulnerability exists in curl 7.33.0 to and including 7.82.0 which might allow reuse OAUTH2-authenticated connections without properly making sure that the connection was authenticated with the same credentials as set for this transfer. This affects SASL-enabled protocols: SMPTP(S), IMAP(S), POP3(S) and LDAP(S) (openldap only).
- Published
- May 26, 2022
- Updated
- Oct 14, 2026
- EPSS
- 2.5% · 84th percentile
- CWE
- CWE-287
Report tools
Action score
33
Monitor
Low priority for now.
- CVSS
- 32 / 40 · 8.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.5%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 8.1
- CNA · hackerone
- 8.1
- 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 |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
| netapp | clustered data ontap | cpe:2.3:a:netapp:clustered_data_ontap |
| netapp | solidfire & hci management node | cpe:2.3:a:netapp:solidfire_&_hci_management_node |
| netapp | solidfire & hci storage node | cpe:2.3:a:netapp:solidfire_&_hci_storage_node |
| broadcom | fabric operating system | cpe:2.3:o:broadcom:fabric_operating_system |
| netapp | bootstrap os | cpe:2.3:o:netapp:bootstrap_os |
| netapp | hci compute node | cpe:2.3:h:netapp:hci_compute_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 |
and 5 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- broadcom fabric operating systemall versions
- debian debian linux10.0
- debian debian linux11.0
- haxx curl7.33.0 and later · before 7.83.0
- netapp bootstrap osall versions
- netapp clustered data ontapall versions
- netapp h300s firmwareall versions
- netapp h410s firmwareall versions
- netapp h500s firmwareall versions
- netapp h700s firmwareall versions
- netapp solidfire & hci management nodeall versions
- netapp solidfire & 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 curl 7.83.0affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | curl | before 7.61.1-22.el8_6.3 | 7.61.1-22.el8_6.3 |
| AlmaLinux:8 | libcurl | before 7.61.1-22.el8_6.3 | 7.61.1-22.el8_6.3 |
| AlmaLinux:8 | libcurl-devel | before 7.61.1-22.el8_6.3 | 7.61.1-22.el8_6.3 |
| AlmaLinux:8 | libcurl-minimal | before 7.61.1-22.el8_6.3 | 7.61.1-22.el8_6.3 |
| Alpine:v3.12 | curl | from 7.33.0 · before 7.79.1-r1 | 7.79.1-r1 |
| Alpine:v3.15 | curl | from 7.33.0 · before 7.80.0-r1 | 7.80.0-r1 |
| Alpine:v3.16 | curl | from 7.33.0 · before 7.83.0-r0 | 7.83.0-r0 |
| Debian:10 | curl | before 7.64.0-4+deb10u3 | 7.64.0-4+deb10u3 |
| Debian:11 | curl | before 7.74.0-1.3+deb11u2 | 7.74.0-1.3+deb11u2 |
| Debian:12 | curl | before 7.83.0-1 | 7.83.0-1 |
| openSUSE:Leap 15.3 | curl | before 7.66.0-150200.4.30.1 | 7.66.0-150200.4.30.1 |
| openSUSE:Tumbleweed | curl | before 7.83.0-1.1 | 7.83.0-1.1 |
| Red Hat:enterprise_linux:8::baseos | curl | before 0:7.61.1-22.el8_6.3 | 0:7.61.1-22.el8_6.3 |
| Red Hat:enterprise_linux:8::baseos | curl-debuginfo | before 0:7.61.1-22.el8_6.3 | 0:7.61.1-22.el8_6.3 |
| Red Hat:enterprise_linux:8::baseos | curl-debugsource | before 0:7.61.1-22.el8_6.3 | 0:7.61.1-22.el8_6.3 |
| Red Hat:enterprise_linux:8::baseos | curl-minimal-debuginfo | before 0:7.61.1-22.el8_6.3 | 0:7.61.1-22.el8_6.3 |
| Red Hat:enterprise_linux:8::baseos | libcurl | before 0:7.61.1-22.el8_6.3 | 0:7.61.1-22.el8_6.3 |
| Red Hat:enterprise_linux:8::baseos | libcurl-debuginfo | before 0:7.61.1-22.el8_6.3 | 0:7.61.1-22.el8_6.3 |
| Red Hat:enterprise_linux:8::baseos | libcurl-devel | before 0:7.61.1-22.el8_6.3 | 0:7.61.1-22.el8_6.3 |
| Red Hat:enterprise_linux:8::baseos | libcurl-minimal | before 0:7.61.1-22.el8_6.3 | 0:7.61.1-22.el8_6.3 |
| Red Hat:enterprise_linux:8::baseos | libcurl-minimal-debuginfo | before 0:7.61.1-22.el8_6.3 | 0:7.61.1-22.el8_6.3 |
| Red Hat:enterprise_linux:9::appstream | curl-debuginfo | before 0:7.76.1-14.el9_0.4 | 0:7.76.1-14.el9_0.4 |
| Red Hat:enterprise_linux:9::appstream | curl-debugsource | before 0:7.76.1-14.el9_0.4 | 0:7.76.1-14.el9_0.4 |
| Red Hat:enterprise_linux:9::appstream | curl-minimal-debuginfo | before 0:7.76.1-14.el9_0.4 | 0:7.76.1-14.el9_0.4 |
+10
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-2021-22946Sep 29, 2021 · A user can tell curl >= 7.20.0 and <= 7.78.0 to require a successful upgrade to TLS when speaking to an IMAP, POP3 or FTP server (`--ssl-req31Monitor
- ← EarlierCVE-2021-22947Sep 29, 2021 · When curl >= 7.20.0 and <= 7.78.0 connects to an IMAP or POP3 server to retrieve data using STARTTLS to upgrade to TLS security, the server 24Monitor
- Later →CVE-2022-27774Jun 2, 2022 · An insufficiently protected credentials vulnerability exists in curl 4.9 to and include curl 7.82.0 are affected that could allow an attacke23Monitor
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 |
|---|---|---|
| almalinux:curl | 7.61.1-22.el8_6.3 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:libcurl | 7.61.1-22.el8_6.3 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:libcurl-devel | 7.61.1-22.el8_6.3 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:libcurl-minimal | 7.61.1-22.el8_6.3 · AlmaLinux:8 | Package registry (OSV) |
| alpine:curl | 7.79.1-r1 · Alpine:v3.12 | Package registry (OSV) |
| debian:curl | 7.83.0-1 · Debian:12 | Package registry (OSV) |
| opensuse:curl | 7.66.0-150200.4.30.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| red hat:curl | 0:7.76.1-14.el9_0.4 · Red Hat:enterprise_linux:9::baseos | Package registry (OSV) |
| red hat:curl-debuginfo | 0:7.76.1-14.el9_0.4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:curl-debugsource | 0:7.76.1-14.el9_0.4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:curl-minimal | 0:7.76.1-14.el9_0.4 · Red Hat:enterprise_linux:9::baseos | Package registry (OSV) |
| red hat:curl-minimal-debuginfo | 0:7.76.1-14.el9_0.4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:libcurl | 0:7.76.1-14.el9_0.4 · Red Hat:enterprise_linux:9::baseos | Package registry (OSV) |
| red hat:libcurl-debuginfo | 0:7.76.1-14.el9_0.4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:libcurl-devel | 0:7.76.1-14.el9_0.4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:libcurl-minimal | 0:7.76.1-14.el9_0.4 · Red Hat:enterprise_linux:9::baseos | Package registry (OSV) |
| red hat:libcurl-minimal-debuginfo | 0:7.76.1-14.el9_0.4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| rocky linux:curl | 0:7.61.1-22.el8_6.3 · Rocky Linux:8 | Package registry (OSV) |
| suse:curl | 7.66.0-150200.4.30.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP3 | 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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-22-0552 · Aug 15, 2022(RedHat Güvenlik Güncellemesi)
- TR-22-0541 · Aug 10, 2022(RedHat Güvenlik Güncellemesi)
- TR-22-0480 · Jul 6, 2022(RedHat Güvenlik Güncellemesi)
- TR-22-0474 · Jul 4, 2022(RedHat Güvenlik Güncellemesi)
- TR-22-0436 · Jun 20, 2022(IBM Güvenlik Bildirimi)
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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-287 · Improper AuthenticationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
nvd-primary
Root cause
Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.
The bug in code
The whole CWE-287 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use("/admin", requireSession, adminRouter);
// Route added later skips the middleware
app.post("/admin-api/config", updateConfig);Fixed
const admin = express.Router();
admin.use(requireSession, requireRole("admin"));
admin.post("/config", updateConfig);
app.use("/admin", admin);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)
- Authentication AbuseCAPEC-114Medium
- Authentication BypassCAPEC-115Medium
- Identity SpoofingCAPEC-151likelihood: Medium · Medium
- Fake the Source of DataCAPEC-194Medium
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Utilizing REST's Trust in the System Resource to Obtain Sensitive DataCAPEC-57likelihood: Medium · Very High
- Session HijackingCAPEC-593likelihood: High · Very High
- Token ImpersonationCAPEC-633Medium
ATT&CK techniques
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.