CVE-2023-6394VulnerabilityPublished 9 Dec 2023Updated 20 Nov 2025

CVE-2023-6394: Red Hat build of Quarkus 2.13.9.Final · Missing Authorization

Affects Red Hat build of Quarkus 2.13.9.FinalSource CVE Database V5

Not known to be exploited · CVSS 7.4 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.4High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.8% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Dec 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

1. Monitor Red Hat security advisories and apply official patches or updates for Quarkus 2.13.9.Final as soon as they become available. 2. Conduct a thorough audit of all GraphQL operations exposed over websockets to ensure explicit role-based permissions are defined and enforced. 3. Implement additional access control mechanisms at the API gateway or reverse proxy level to restrict unauthenticated websocket connections. 4. Use network segmentation and firewall rules to limit exposure of websocket endpoints to trusted networks or authenticated users only. 5. Employ runtime application self-protection (RASP) or Web Application Firewalls (WAFs) capable of detecting and blocking unauthorized GraphQL requests. 6. Review and enhance logging and monitoring for websocket connections and GraphQL operations to detect anomalous or unauthorized access attempts. 7. Educate development teams on secure API design principles, emphasizing the necessity of explicit authorization checks on all operations. 8. If immediate patching is not possible, consider disabling websocket support for GraphQL or restricting its use until a fix is applied.

Description

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

For European organizations, the impact of CVE-2023-6394 can be significant, especially for those deploying cloud-native applications using Red Hat's Quarkus framework with GraphQL APIs over websockets. Unauthorized access to sensitive data or critical functionality can lead to data breaches, intellectual property theft, or unauthorized manipulation of business logic. Confidentiality and integrity are at high risk, potentially affecting customer data, internal systems, and compliance with data protection regulations such as GDPR. The vulnerability could also undermine trust in digital services and lead to financial and reputational damage. Since the attack vector is network-based and requires no authentication or user interaction, exploitation could be automated and widespread if attackers develop exploits. The lack of availability impact reduces the risk of service disruption but does not diminish the seriousness of unauthorized data access. Organizations in sectors such as finance, healthcare, government, and critical infrastructure that rely on Quarkus for API services are particularly vulnerable. The timing of patch availability and the speed of deployment will critically influence the extent of impact.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 20 Nov 2025, 07:57 UTC

Technical details

References

Community reviews

Related threats