VulnerabilityPublished 23 Jan 2024Updated 30 May 2025

CVE-2023-31654: Redis raft master-1b8bd86 to master-7b46079 was discovered to contain an ODR violation via the

Source CVE Database V5

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 3.1 base score

9.8Critical

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

EPSS: 0.6% chance of exploitation in 30 days – higher than 49% 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:H/I:H/A:H

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

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: 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: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 23 Jan 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

AI-suggested

European organizations should take the following specific actions: 1) Immediately identify and inventory all Redis deployments, focusing on those using the Redis Raft module. 2) Monitor official Redis and hiredis repositories and security advisories for patches addressing this ODR violation and apply them promptly. 3) If patches are not yet available, consider disabling or isolating Redis Raft components until a fix is released. 4) Employ network segmentation and firewall rules to restrict access to Redis instances, limiting exposure to untrusted networks. 5) Implement strict access controls and authentication mechanisms around Redis services to reduce the attack surface. 6) Conduct thorough code reviews and rebuild Redis Raft and hiredis components from trusted sources to avoid binary inconsistencies that may trigger ODR issues. 7) Deploy runtime monitoring and anomaly detection to identify unusual Redis behavior indicative of exploitation attempts. 8) Prepare incident response plans specifically for Redis-related compromises, including data backup and recovery strategies. These steps go beyond generic advice by focusing on the unique nature of the ODR violation and the criticality of the Redis Raft module in distributed environments.

Description

Redis raft master-1b8bd86 to master-7b46079 was discovered to contain an ODR violation via the component hiredisAllocFns at /opt/fs/redisraft/deps/hiredis/alloc.c.

Impact

For European organizations, the impact of CVE-2023-31654 can be severe, especially for those relying on Redis Raft for distributed caching, session management, or stateful applications. Exploitation can lead to unauthorized remote code execution, data breaches, loss of data integrity, and denial of service, severely disrupting business operations. Critical infrastructure, financial institutions, e-commerce platforms, and cloud service providers in Europe that use Redis Raft could face significant operational downtime and data compromise. Given the vulnerability requires no authentication and no user interaction, attackers can exploit it remotely at scale, increasing the risk of widespread attacks. The high confidentiality impact means sensitive customer or operational data could be exposed, violating GDPR and other data protection regulations, leading to legal and financial penalties. The integrity and availability impacts threaten the reliability of services, potentially causing cascading failures in dependent systems. The absence of known exploits in the wild currently provides a small window for mitigation, but the critical severity demands immediate attention to prevent future attacks.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 8 Jul 2025, 16:25 UTC

Technical details

References

Community reviews

Related threats