Privilege escalation via cross-request context reuse
Published Mar 23, 2022 · Updated Aug 2, 2024
Incorrect authorization in Quarkus before 2.7.1.Final allows remote authenticated users to perform database operations with unintended privileges. RESTEasy Reactive associates request-scoped state with the wrong Vert.x context during concurrent requests, allowing one request's state and permissions to be reused by another. Exploitation requires a low-privileged account and an application using RESTEasy Reactive with database-backed authorization under concurrent request load.
Summary
What happened
Incorrect authorization in Quarkus before 2.7.1.Final allows remote authenticated users to perform database operations with unintended privileges. RESTEasy Reactive associates request-scoped state with the wrong Vert.x context during concurrent requests, allowing one request's state and permissions to be reused by another. Exploitation requires a low-privileged account and an application using RESTEasy Reactive with database-backed authorization under concurrent request load.
The record
- CVE
- CVE-2022-0981
- Published
- Mar 23, 2022
- Updated
- Aug 2, 2024
- Vendor
- Red Hat
- Product
- Quarkus
- Classifications
- CWE-863, T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 23, 2022CVE publishedPublication date reported by the CVE source.
- Aug 2, 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.7.1.Final
What conditions does exploitation require?
What is affected?
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
- Concurrent-request Hibernate Reactive reproducerproof 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