What is CVE-2023-6394?

CVE-2023-6394 is a high-severity missing authorization vulnerability in io.quarkus:quarkus-smallrye-graphql-client (maven), affecting versions >= 2.14.0, < 3.5.3. It is fixed in 3.5.3, 2.13.9.Final. The application does not perform an authorization check before performing a sensitive operation.

How severe is CVE-2023-6394?

CVE-2023-6394 has a CVSS score of 7.4 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of io.quarkus:quarkus-smallrye-graphql-client are affected by CVE-2023-6394?

io.quarkus:quarkus-smallrye-graphql-client (maven) versions >= 2.14.0, < 3.5.3 is affected.

Is there a fix for CVE-2023-6394?

Yes. CVE-2023-6394 is fixed in 3.5.3, 2.13.9.Final. Upgrade to this version or later.

Is CVE-2023-6394 exploitable, and should I be worried?

Whether CVE-2023-6394 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2023-6394 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2023-6394

Q: How severe is CVE-2023-6394?

CVE-2023-6394 has a CVSS score of 7.4 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of io.quarkus:quarkus-smallrye-graphql-client are affected by CVE-2023-6394?

io.quarkus:quarkus-smallrye-graphql-client (maven) versions >= 2.14.0, < 3.5.3 is affected.

Q: Is there a fix for CVE-2023-6394?

Yes. CVE-2023-6394 is fixed in 3.5.3, 2.13.9.Final. Upgrade to this version or later.

Q: Is CVE-2023-6394 exploitable, and should I be worried?

Whether CVE-2023-6394 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2023-6394 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2023-6394?

Upgrade: io.quarkus:quarkus-smallrye-graphql-client to 3.5.3 or later, io.quarkus:quarkus-smallrye-graphql-client to 2.13.9.Final or later.

Summary

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.

Impact

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

CVE-2023-6394 has a CVSS score of 7.4 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.5.3, 2.13.9.Final); upgrading removes the vulnerable code path.

Affected versions

io.quarkus:quarkus-smallrye-graphql-client (>= 2.14.0, < 3.5.3) io.quarkus:quarkus-smallrye-graphql-client (< 2.13.9.Final)

Security releases

io.quarkus:quarkus-smallrye-graphql-client → 3.5.3 (maven) io.quarkus:quarkus-smallrye-graphql-client → 2.13.9.Final (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

io.quarkus:quarkus-smallrye-graphql-client to 3.5.3 or later; io.quarkus:quarkus-smallrye-graphql-client to 2.13.9.Final or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2023-6394? CVE-2023-6394 is a high-severity missing authorization vulnerability in io.quarkus:quarkus-smallrye-graphql-client (maven), affecting versions >= 2.14.0, < 3.5.3. It is fixed in 3.5.3, 2.13.9.Final. The application does not perform an authorization check before performing a sensitive operation.
How severe is CVE-2023-6394? CVE-2023-6394 has a CVSS score of 7.4 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of io.quarkus:quarkus-smallrye-graphql-client are affected by CVE-2023-6394? io.quarkus:quarkus-smallrye-graphql-client (maven) versions >= 2.14.0, < 3.5.3 is affected.
Is there a fix for CVE-2023-6394? Yes. CVE-2023-6394 is fixed in 3.5.3, 2.13.9.Final. Upgrade to this version or later.
Is CVE-2023-6394 exploitable, and should I be worried? Whether CVE-2023-6394 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2023-6394 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2023-6394?
- Upgrade io.quarkus:quarkus-smallrye-graphql-client to 3.5.3 or later
- Upgrade io.quarkus:quarkus-smallrye-graphql-client to 2.13.9.Final or later