Authorization spoofing via duplicate headers
Published Oct 7, 2021 · Updated Aug 4, 2024
Authentication bypass in Google Cloud Extensible Service Proxy before 1.58.0 allows remote authenticated users to spoof authorization claims. ESPv1 replaces only the first X-Endpoint-API-UserInfo header, allowing a client-supplied duplicate header with a forged JWT claim to reach the backend. Exploitation requires a JWT that ESP accepts and a backend that uses this header for authorization, enabling unauthorized access without direct ESP configuration changes.
Summary
What happened
Authentication bypass in Google Cloud Extensible Service Proxy before 1.58.0 allows remote authenticated users to spoof authorization claims. ESPv1 replaces only the first X-Endpoint-API-UserInfo header, allowing a client-supplied duplicate header with a forged JWT claim to reach the backend. Exploitation requires a JWT that ESP accepts and a backend that uses this header for authorization, enabling unauthorized access without direct ESP configuration changes.
The record
- CVE
- CVE-2021-41130
- Published
- Oct 7, 2021
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Extensible Service Proxy
- Classifications
- CWE-290, T1606
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 7, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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.58.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