CVE-2023-4344: Broadcom LSI Storage Authority (LSA) · Insufficient Entropy
Affects Broadcom LSI Storage Authority (LSA)Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 14:05 UTC
- 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:HExploitation evidence
Disclosed: evidence found.
CVE published 15 Aug 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Broadcom LSI Storage Authority (LSA) | Affected
| Fixed in– |
AI-suggested
2) Disable remote management features if not essential, or enforce VPN and multi-factor authentication for any remote access to reduce exposure. 3) Monitor network traffic for anomalous SSL session behaviors or unexpected CIM connection attempts that could indicate exploitation attempts. 4) Engage with Broadcom support to obtain any interim fixes or guidance and subscribe to vendor advisories for patch releases. 5) Conduct thorough audits of RAID controller configurations and logs to detect any signs of compromise. 6) Plan for rapid deployment of patches once available and integrate this vulnerability into incident response and risk management frameworks. These targeted actions go beyond generic advice by focusing on access control, monitoring, and vendor engagement specific to the affected product and vulnerability nature.
Description
Broadcom RAID Controller web interface is vulnerable to insufficient randomness due to improper use of ssl.rnd to setup CIM connection