VulnerabilityPublished 10 Apr 2024Updated 20 Nov 2025

CVE-2023-6236: Red Hat JBoss Enterprise Application Platform 8 jboss-eap · Insufficient Verification of Data Authenticity

Affects Red Hat JBoss Enterprise Application Platform 8 jboss-eapSource CVE Database V5

Not known to be exploited · CVSS 7.3 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

7.3High

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

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

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

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

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: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Apr 2024
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 26 Oct 2026.

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 or the CVSS exploit maturity 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

Affected software

Product	Affected	Fixed in
Red Hatredhat/jboss-eap`pkg:rpm/redhat/jboss-eap`Other threats	Affected =8	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2023-6236, European organizations should immediately assess their use of Red Hat JBoss EAP 8 in multi-tenant OIDC environments. The primary mitigation is to apply official patches or updates from Red Hat that correct the OidcSessionTokenStore logic to consider both 'provider-url' and 'realm' parameters when validating cached tokens. If patches are not yet available, organizations should consider temporarily disabling multi-tenant OIDC configurations or enforcing strict session isolation policies to prevent token reuse across tenants. Reviewing and tightening OIDC session management configurations can help reduce risk. Implementing additional monitoring and alerting for anomalous authentication behavior or cross-tenant access attempts is recommended. Conducting thorough testing of authentication flows after applying fixes ensures that tenant isolation is properly enforced. Organizations should also audit their access logs for any suspicious activity related to token reuse. Finally, educating developers and administrators about secure multi-tenant authentication practices and the specifics of this vulnerability will help prevent similar issues in the future.

Description

CVE-2023-6236 is a high-severity vulnerability in Red Hat JBoss Enterprise Application Platform 8 related to insufficient verification of data authenticity in its OpenID Connect (OIDC) implementation. The flaw arises when a multi-tenant OIDC application accesses a second tenant secured by a different OIDC configuration but fails to prompt for re-authentication due to improper token validation logic. Specifically, the OidcSessionTokenStore component does not consider the new 'provider-url' parameter alongside the 'realm' parameter when deciding to reuse cached tokens, potentially allowing unauthorized access across tenants. This vulnerability does not affect EAP-7, which lacks the vulnerable 'provider-url' option. The CVSS 3.1 score is 7.3 (high), reflecting network exploitability without authentication or user interaction, and impacts confidentiality, integrity, and availability. No known exploits are reported in the wild yet. European organizations using Red Hat JBoss EAP 8 for multi-tenant OIDC applications should prioritize patching and reviewing their authentication flows to prevent cross-tenant token misuse.

Impact

For European organizations, the impact of CVE-2023-6236 can be substantial, especially for those deploying multi-tenant applications using Red Hat JBoss EAP 8 with OIDC authentication. Unauthorized token reuse across tenants can lead to cross-tenant data leakage, exposing sensitive personal data or business-critical information, which may violate GDPR and other data protection regulations. This breach of tenant isolation could result in reputational damage, regulatory fines, and loss of customer trust. Additionally, attackers exploiting this flaw could manipulate or disrupt tenant-specific services, impacting business continuity. The network-exploitable nature of the vulnerability means attackers can attempt exploitation remotely without authentication or user interaction, increasing the attack surface. Organizations in sectors such as finance, healthcare, government, and critical infrastructure that rely on multi-tenant JBoss EAP 8 deployments are particularly at risk. The absence of known exploits in the wild provides a window for proactive mitigation, but the high severity score underscores the urgency to address this vulnerability to prevent potential data breaches and service disruptions.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Nov 2025, 18:34 UTC

Technical details

References

Community reviews

Related threats