Authorization bypass in Quarkus
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2023-6394US | critical9.1OT elevated | — | ||
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 reque… | ||||
02
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/errata/RHSA-2023:7612WEB
- https://access.redhat.com/errata/RHSA-2023:7700WEB
- https://access.redhat.com/security/cve/CVE-2023-6394WEB
- https://bugzilla.redhat.com/show_bug.cgi?id=2252197WEB
- https://github.com/quarkusio/quarkusPACKAGE
- https://github.com/quarkusio/quarkus/pull/36961WEB
- https://github.com/quarkusio/quarkus/releases/tag/2.13.9.FinalWEB
- https://github.com/quarkusio/quarkus/releases/tag/3.5.3WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan