Unauthenticated endpoint access via unvalidated bearer tokens
Published Jun 9, 2022 · Updated Apr 23, 2025
Authentication bypass in Envoy before 1.22.1 allows remote attackers to access OAuth-protected endpoints with an arbitrary bearer token. OAuth2Filter::decodeHeaders treated any Authorization bearer value as a completed flow and continued decoding without validating the token or requiring the HMAC-signed cookie. The OAuth filter must protect the requested endpoint; exploitation grants that endpoint's normal read or write access without authentication.
Summary
What happened
Authentication bypass in Envoy before 1.22.1 allows remote attackers to access OAuth-protected endpoints with an arbitrary bearer token. OAuth2Filter::decodeHeaders treated any Authorization bearer value as a completed flow and continued decoding without validating the token or requiring the HMAC-signed cookie. The OAuth filter must protect the requested endpoint; exploitation grants that endpoint's normal read or write access without authentication.
The record
- CVE
- CVE-2022-29226
- Published
- Jun 9, 2022
- Updated
- Apr 23, 2025
- Vendor
- Envoy Proxy
- Product
- Envoy
- Classifications
- CWE-306, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 9, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record 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=< 1.22.1
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
- Arbitrary bearer-token curl proof of conceptproof of concept · demonstrated
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