Cyber Resilience

CVE-2023-4344

Crypto Weakness in Broadcom Raid Controller Web Interface 51.12.0-2779

Published
15 August 2023
Modified
04 November 2025
Patch / advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0059 45th percentile
Risk Priority 70 floored blend · peak EPSS

Summary

CVE-2023-4344 is a critical-severity Insufficient Entropy (CWE-331) vulnerability in Broadcom Raid Controller Web Interface. Its CVSS base score is 9.8 (Critical).

Operationally, ranked at the 45th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Broadcom RAID Controller web interface is vulnerable to insufficient randomness due to improper use of ssl.rnd to setup CIM connection

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-4334Same product: Broadcom Raid Controller Web Interface
CVE-2023-4331Same product: Broadcom Raid Controller Web Interface
CVE-2023-4343Same product: Broadcom Raid Controller Web Interface
CVE-2023-4339Same product: Broadcom Raid Controller Web Interface
CVE-2023-4325Same product: Broadcom Raid Controller Web Interface
CVE-2023-4323Same product: Broadcom Raid Controller Web Interface
CVE-2023-4345Same product: Broadcom Raid Controller Web Interface
CVE-2023-4336Same product: Broadcom Raid Controller Web Interface
CVE-2023-4342Same product: Broadcom Raid Controller Web Interface
CVE-2023-4324Same product: Broadcom Raid Controller Web Interface

Affected Assets

broadcom
raid controller web interface
51.12.0-2779

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 14 hardening rules · 5 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V6.5.2
  • V11.3.4

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-330 CWE-331

Key generation under controlled management uses approved random-bit sources rather than insufficiently random values.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices explicitly include vetted RNG and entropy sources, directly preventing this weakness while covering many other development concerns.

PR.AA-03 partial match
prevents

Password-strength policies implicitly require sufficient entropy, but the control addresses authentication rather than algorithmic randomness.

PR.DS-01 partial match
prevents

Proper encryption for data-at-rest requires sufficient entropy for keys/nonces; eliminating the weakness therefore supports but does not fully realize the control.

PR.DS-02 partial match
prevents

Cryptographic protection of data-in-transit depends on adequate entropy; the weakness directly undermines the control's effectiveness.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Mandates use of cryptography that must rely on sufficient entropy sources.

detects

Security testing can detect insufficient-entropy defects before release.

prevents

Secure-SDLC activities include entropy validation during design and testing.

prevents

Secure-coding rules can explicitly forbid weak random-number generation.

degrades

Requires secure authentication mechanisms that depend on unpredictable secrets.

Hardening callouts derived

Configuration rules from DISA STIG baselines that reduce the attack surface for weaknesses of the type cited by this CVE. Derived transitively via CVE→CWE→STIG over `controls_xwalks` (authoritative rows only).

Oracle Linux 8 (1 rule)
  • V-248524 OL 8 must implement NIST FIPS-validated cryptography for the following: To provision digital signatures, to generate cryptographic hashes, and to protect data requiring data-at-rest protections in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. via CWE-331
RHEL 8 (1 rule)
  • V-230223 RHEL 8 must implement NIST FIPS-validated cryptography for the following: To provision digital signatures, to generate cryptographic hashes, and to protect data requiring data-at-rest protections in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. via CWE-331

References