Unauthenticated API access via method override routing
Published Apr 26, 2023 · Updated Feb 3, 2025
Authentication bypass in Google Cloud ESPv2 2.20.0 through 2.42.0 allows remote attackers to reach JWT-protected API methods. The filter chain handled X-HTTP-Method-Override after JWT route matching, so authentication used the undefined original method while later routing accepted the defined override. Exposure requires JWT authentication and that method mismatch; API-key restrictions are unaffected, while protected backend data and actions become accessible.
Summary
What happened
Authentication bypass in Google Cloud ESPv2 2.20.0 through 2.42.0 allows remote attackers to reach JWT-protected API methods. The filter chain handled X-HTTP-Method-Override after JWT route matching, so authentication used the undefined original method while later routing accepted the defined override. Exposure requires JWT authentication and that method mismatch; API-key restrictions are unaffected, while protected backend data and actions become accessible.
The record
- CVE
- CVE-2023-30845
- Published
- Apr 26, 2023
- Updated
- Feb 3, 2025
- Vendor
- Google Cloud
- Product
- Extensible Service Proxy V2 (ESPv2)
- Classifications
- CWE-287, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 26, 2023CVE publishedPublication date reported by the CVE source.
- Feb 3, 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=>= 2.20.0, < 2.43.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.
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