CVE-2024-3411Patch

LOWCVSS 9.1 · CRITICAL

Signal is active with 1 mentions in latest observed window

Immediate actions

Patch affected systems immediately

Recommended action window: Monitor and triage in normal cycle

NVD 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.

Back to dashboard

0.5/ 10 priority

Sources & remediation

Other references

Weakness type (CWE)

CWE-331

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

NONE

Threat summary

Patch or workaround signal is available
1 mentions across 1 observed day

What's happening

Patch or workaround mentioned in 1 signal
1 total mentions across 1 day

Deep dive

Activity timeline1 mentions / 1d

Signal classification1 categories

Patch

1100.0%

Full discourse1 post

Zero Hunt@zerohuntai91d
Patch
The fix, honestly: - CVE-2013-4786: nothing. Ever. It's the specification. - Patchable: BMC firmware — closes CVE-2024-3411 (9.1), not the RAKP leak. - Actual removal: move to Redfish, disable IPMI-over-LAN. No lockout applies. Every guess runs on their GPU, not yours.
Post summary
The post describes a firmware patch that fixes CVE‑2024‑3411, recommends disabling IPMI‑over‑LAN and adopting Redfish, while noting that CVE‑2013‑4786 is not a real exploit and thus is not a concern.
1000035
12 followersView on X

Explore more

Back to dashboard