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 secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/quarkus | <3.6.0 | 3.6.0 |
Quarkus Quarkus | <3.6.0 | |
Redhat Build Of Quarkus | ||
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 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.