CVE-2023-6394GHSA-MVC8-6FFP-JRX5
Quarkus: graphql operations over websockets bypass
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.5.3, 2.13.9.Final
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
A flaw was found in Quarkus. This issue occurs when receiving a request over websocket with no role-based permission specified on the GraphQL operation, Quarkus processes the request without authentication despite the endpoint being secured. This can allow an attacker to access information and functionality outside of normal granted API permissions.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Red Hat Red Hat build of Quarkus 2.13.9
Version range not reported
- io.quarkus/quarkus-smallrye-graphql
Version range not reported
- graphql-java
Version range not reported
- io.quarkus:quarkus-smallrye-graphql-clientMaven
From 2.14.0 · fixed in 3.5.3
- io.quarkus:quarkus-smallrye-graphql-clientMaven
fixed in 2.13.9.Final