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.
Weakness
If a web server does not fully parse requested URLs before it examines them for authorization, it may be possible for an attacker to bypass authorization protection.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Quarkus | Quarkus | * | 3.6.0 (excluding) |
| Red Hat build of Quarkus 2.13.9.Final | RedHat | io.quarkus/quarkus-smallrye-graphql:2.13.9.Final-redhat-00002 | * |
| Red Hat build of Quarkus 3.2.9.Final | RedHat | io.quarkus/quarkus-smallrye-graphql:3.2.9.Final-redhat-00002 | * |
Potential Mitigations
References
- https://access.redhat.com/errata/RHSA-2023:7612
- https://access.redhat.com/errata/RHSA-2023:7700
- https://access.redhat.com/security/cve/CVE-2023-6394
- https://bugzilla.redhat.com/show_bug.cgi?id=2252197
- https://access.redhat.com/errata/RHSA-2023:7612
- https://access.redhat.com/security/cve/CVE-2023-6394
- https://bugzilla.redhat.com/show_bug.cgi?id=2252197