Build Of QuarkusApplication · Redhat
CVE-2023-6394
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA critical authentication bypass vulnerability in Quarkus where GraphQL operations accessed via WebSocket are processed without authentication when no role-based permission is specified, even if the endpoint is secured. This allows unauthenticated or unauthorized attackers to access sensitive API functionality.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Build Of QuarkusApplication
all versions< 3.6.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Quarkus GraphQL dependency usageSearch your project build files (pom.xml, build.gradle, etc.) for the smallrye-graphql dependency or Quarkus GraphQL extensionAffected if The smallrye-graphql or quarkus-graphql-hibernate dependency is present in your project dependencies
-
Check if GraphQL WebSocket transport is enabledLook for configuration property 'quarkus.graphql.ws.enabled' set to 'true' in your application.properties or application.yaml files, or check for the quarkus-graphql-hibernate-runtime dependency which may enable WebSocket by defaultAffected if GraphQL WebSocket transport is enabled in your Quarkus configuration
-
Determine your Quarkus versionCheck your pom.xml or build.gradle for the quarkus-bom or quarkus-core version, or run 'mvn quarkus:info' if available, and compare against the affected range: all versions for Red Hat Build of Quarkus, or < 3.6.0 for QuarkusAffected if Your Quarkus version is below 3.6.0, or you are using Red Hat Build of Quarkus of any version with GraphQL WebSocket enabled
-
Inspect GraphQL operation definitions for missing role permissionsExamine your GraphQL API classes (classes annotated with @GraphQLApi or containing @Query, @Mutation methods) and verify whether @RolesAllowed, @Authenticated, or other security annotations are explicitly defined on GraphQL entry point methodsAffected if GraphQL operations do not have explicit @RolesAllowed, @Authenticated, or security role definitions, even when the overall endpoint is secured
You are affected if you use Quarkus with GraphQL WebSocket enabled, your version is below 3.6.0 (or any version of Red Hat Build of Quarkus), and GraphQL operations lack explicit role-based access permissions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.6.0
Audit all GraphQL operations and explicitly define role-based access permissions on each operation, particularly for WebSocket endpoints, to ensure authentication is properly enforced.
Quarkus 3.6.0
- Upgrade Quarkus to version 3.6.0 or later to resolve the missing authorization vulnerability in GraphQL over WebSocket endpoints
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Build Of Quarkus
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-6394 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-6394 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data