VulnerabilityPublished 30 Apr 2024Updated 4 Nov 2025

CVE-2024-3411: Dell iDRAC8 · Insufficient Entropy

Affects Dell iDRAC8Source CVE Database V5

Not known to be exploited · CVSS 9.1 Critical.

Data as of 26 Oct 2026, 12:29 UTC

CVSS 3.1 base score

9.1Critical

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

EPSS: 0.7% chance of exploitation in 30 days – higher than 53% 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:N

Attack Vector: Network
Attack Complexity: Low
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: 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: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 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
Dell iDRAC8	Affected =2.86.86.86	Fixed in–

AI-suggested

Immediately restrict network access to iDRAC interfaces by implementing strict firewall rules and network segmentation to limit exposure only to trusted management networks.
Disable IPMI or iDRAC remote management interfaces if not actively used or required.
Monitor network traffic for anomalous IPMI packets or session activity that could indicate attempted exploitation.
Apply any available firmware updates or patches from Dell as soon as they are released; maintain close communication with Dell support for updates on remediation.
Implement strong authentication and encryption controls around management interfaces where possible, including VPNs or jump hosts for remote access.
Conduct regular audits of server management configurations to ensure compliance with security best practices.
Consider deploying intrusion detection/prevention systems tuned to detect IPMI protocol anomalies.
Educate IT staff about the risks of exposing management interfaces and the importance of timely patching and network controls.

Description

Implementations of IPMI Authenticated sessions does not provide enough randomness to protect from session hijacking, allowing an attacker to use either predictable IPMI Session ID or weak BMC Random Number to bypass security controls using spoofed IPMI packets to manage BMC device.

Impact

For European organizations, the impact of CVE-2024-3411 can be severe. Many enterprises, data centers, and critical infrastructure operators rely on Dell servers equipped with iDRAC8 for remote management. Successful exploitation could allow attackers to gain unauthorized control over server hardware, bypassing operating system-level security controls. This can lead to unauthorized system reboots, configuration changes, or data exfiltration at the hardware management level, severely compromising confidentiality and integrity. The availability impact is rated low since the vulnerability does not directly cause denial of service, but indirect availability issues may arise from malicious reboots or misconfigurations. Given the network-based attack vector and no requirement for authentication, attackers can exploit this vulnerability remotely if the iDRAC interface is exposed or accessible within internal networks. This risk is heightened in environments where iDRAC interfaces are not properly segmented or protected. European organizations in sectors such as finance, telecommunications, government, and energy, which often use Dell hardware, face elevated risks. The vulnerability could also be leveraged as a foothold for further lateral movement or persistent access within networks.

CWE-331Insufficient Entropy (opens in a new tab)
Base weaknessOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product uses an algorithm or scheme that produces insufficient entropy, leaving patterns or clusters of values that are more likely to occur than others.
Implementation
Determine the necessary entropy to adequately provide for randomness and predictability. This can be achieved by increasing the number of bits of objects such as keys and seeds.
OWASP Cheat Sheets
Session Management (opens in a new tab)
Transport Layer Protection (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
Cryptographic Storage (opens in a new tab)
OWASP ASVS 4.0.3
V3.2.2 (opens in a new tab)
V3.2.4 (opens in a new tab)
V2.3.1 (opens in a new tab)
Attack patterns
Session Credential Falsification through Prediction (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2025, 18:00 UTC

WeaknessesCWE-331

Technical details

References

Community reviews

Related threats