Authentication bypass via unchecked cached OAuth bearer
Published May 26, 2022 · Updated May 27, 2026
Improper authentication in libcurl in curl 7.33.0 through 7.82.0 allows remote authenticated users to bypass OAuth2 checks. ConnectionExists compares only the username and password when selecting a cached SASL connection, omitting the authorization identity and OAuth bearer. A prior successful OAuth2 login and a later transfer to the same SMTP(S), IMAP(S), POP3(S), or OpenLDAP LDAP(S) endpoint are required, allowing the first transfer's connection to authorize the second.
Summary
What happened
Improper authentication in libcurl in curl 7.33.0 through 7.82.0 allows remote authenticated users to bypass OAuth2 checks. ConnectionExists compares only the username and password when selecting a cached SASL connection, omitting the authorization identity and OAuth bearer. A prior successful OAuth2 login and a later transfer to the same SMTP(S), IMAP(S), POP3(S), or OpenLDAP LDAP(S) endpoint are required, allowing the first transfer's connection to authorize the second.
The record
- CVE
- CVE-2022-22576
- Published
- May 26, 2022
- Updated
- May 27, 2026
- Vendor
- curl
- Product
- curl
- Classifications
- CWE-305, T1550.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 26, 2022CVE publishedPublication date reported by the CVE source.
- May 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Fixed in curl 7.83.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo