First published: Thu Nov 30 2023(Updated: )
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.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/quarkus | <3.6.0 | 3.6.0 |
maven/io.quarkus:quarkus-smallrye-graphql-client | <2.13.9.Final | 2.13.9.Final |
maven/io.quarkus:quarkus-smallrye-graphql-client | >=2.14.0<3.5.3 | 3.5.3 |
Red Hat Quarkus | <3.6.0 | |
Red Hat Quarkus |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-6394 has been classified as a high-severity vulnerability due to its potential to allow unauthorized access.
To fix CVE-2023-6394, upgrade to Quarkus version 3.6.0 or later, or use specific patched versions for the affected GraphQL client dependencies.
Applications using Quarkus with GraphQL operations lacking role-based permission specifications are vulnerable to CVE-2023-6394.
Yes, CVE-2023-6394 can be exploited remotely since it involves receiving unauthenticated requests over a websocket.
The impact of CVE-2023-6394 can lead to unauthorized access to sensitive information due to the lack of proper authentication.