Authentication context leakage via stale GraphQL context
Published Aug 31, 2022 · Updated Aug 3, 2024
Improper request context handling in Quarkus 2.10.0 through 2.10.3 allows remote attackers to inherit authentication context via exposed GraphQL services. The SmallRye GraphQL extension fails to terminate request context, so later requests on the same thread reuse headers and authentication from the first request. Exploitation requires a deployed GraphQL endpoint and can expose protected data or authorize actions under another request's identity.
Summary
What happened
Improper request context handling in Quarkus 2.10.0 through 2.10.3 allows remote attackers to inherit authentication context via exposed GraphQL services. The SmallRye GraphQL extension fails to terminate request context, so later requests on the same thread reuse headers and authentication from the first request. Exploitation requires a deployed GraphQL endpoint and can expose protected data or authorize actions under another request's identity.
The record
- CVE
- CVE-2022-2466
- Published
- Aug 31, 2022
- Updated
- Aug 3, 2024
- Vendor
- Red Hat
- Product
- Quarkus
- Classifications
- CWE-444
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 31, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=quarkus 2.10.3
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