CVE-2023-4586VulnerabilityPublished 4 Oct 2023Updated 20 Nov 2025

CVE-2023-4586: Red Hat Data Grid 8.4.6 · Improper Input Validation

Affects Red Hat Data Grid 8.4.6Source CVE Database V5

Not known to be exploited · CVSS 7.4 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

7.4High

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

EPSS: 0.5% chance of exploitation in 30 days – higher than 45% 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 4 Oct 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-26.

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

To mitigate CVE-2023-4586, organizations should take the following specific actions: 1) Monitor Red Hat’s official channels closely for patches or updates addressing this vulnerability and apply them promptly once available. 2) In the interim, review and enforce TLS configuration settings in the Hot Rod client to ensure hostname validation is explicitly enabled if configurable. 3) Employ network-level protections such as strict TLS interception policies and use of network segmentation to limit exposure of Red Hat Data Grid communications. 4) Implement network monitoring and intrusion detection systems to identify anomalous traffic patterns indicative of MITM attempts. 5) Conduct security audits and penetration tests focusing on TLS configurations and certificate validation processes within the affected environment. 6) Educate system administrators and DevOps teams about the importance of TLS hostname validation and secure client configurations. 7) Where feasible, use mutual TLS authentication to add an additional layer of verification between clients and servers. These measures go beyond generic advice by focusing on configuration hardening, monitoring, and operational readiness until patches are deployed.

Description

A vulnerability was found in the Hot Rod client. This security issue occurs as the Hot Rod client does not enable hostname validation when using TLS, possibly resulting in a man-in-the-middle (MITM) attack.

Impact

For European organizations, the impact of CVE-2023-4586 is considerable, especially for those relying on Red Hat Data Grid for critical data caching and distributed data management. The vulnerability compromises the confidentiality and integrity of data transmitted over TLS by allowing MITM attacks, which can lead to data leakage, unauthorized data manipulation, or injection of malicious data. This is particularly concerning for sectors such as finance, healthcare, telecommunications, and government services where sensitive or regulated data is frequently transmitted. The lack of hostname validation undermines trust in secure communications, potentially exposing internal communications and business-critical operations to espionage or sabotage. Additionally, the vulnerability could be leveraged as a foothold for further lateral movement within enterprise networks. Given the widespread use of Red Hat products in European enterprises and public sector organizations, the threat could have broad implications if exploited. The absence of known exploits in the wild provides a window for proactive mitigation, but the risk remains high due to the ease of remote exploitation without authentication.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 20 Nov 2025, 19:03 UTC

Technical details

References

Community reviews

Related threats