CVE-2023-3628VulnerabilityPublished 18 Dec 2023Updated 7 Nov 2025

CVE-2023-3628: Red Hat Data Grid 8.4.4 · Missing Critical Step in Authentication

Affects Red Hat Data Grid 8.4.4Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.5Medium

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

EPSS: 0.7% 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:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
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: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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: None: There is no loss of integrity within 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 18 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. Apply official patches or updates from Red Hat as soon as they become available to address the permission evaluation flaw in the REST bulk read endpoints. 2. Until patches are deployed, restrict access to the Red Hat Data Grid REST API by implementing network-level controls such as firewalls, VPNs, or IP whitelisting to limit exposure to trusted users only. 3. Enforce strict authentication and authorization policies, ensuring that only necessary users have access to the REST API and that their permissions are correctly configured and regularly audited. 4. Implement monitoring and logging of REST API access to detect unusual bulk read operations or access patterns indicative of exploitation attempts. 5. Consider deploying Web Application Firewalls (WAFs) or API gateways that can enforce additional access controls and rate limiting on REST endpoints. 6. Review and harden the configuration of Red Hat Data Grid deployments, disabling unnecessary endpoints or features that are not in use. 7. Conduct regular security assessments and penetration testing focusing on API security to identify and remediate similar issues proactively.

Description

A flaw was found in Infinispan's REST. Bulk read endpoints do not properly evaluate user permissions for the operation. This issue could allow an authenticated user to access information outside of their intended permissions.

Impact

For European organizations, the primary impact is unauthorized disclosure of sensitive or confidential data managed within Red Hat Data Grid 8.4.4 environments. This could affect sectors such as finance, healthcare, government, and critical infrastructure where data confidentiality is paramount. The vulnerability could lead to compliance violations under GDPR if personal or sensitive data is exposed. Although the vulnerability does not affect data integrity or availability, the breach of confidentiality can undermine trust, cause reputational damage, and potentially lead to financial penalties. Organizations using Red Hat Data Grid in multi-tenant or shared environments are particularly at risk, as users with limited privileges might access data belonging to other tenants. The remote exploitability without user interaction increases the risk of automated or scripted attacks if the REST API is exposed to untrusted networks. Overall, the vulnerability poses a moderate but tangible threat to data security in European enterprises relying on this technology.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 7 Nov 2025, 11:09 UTC

Technical details

References

Community reviews

Related threats