dbcve.org
Raid Controller Web InterfaceApplication · Broadcom

CVE-2023-4326

HIGH · 7.5 CVSS v3.1 Published 2023-08-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Broadcom RAID Controller web interface is vulnerable has an insecure default TLS configuration that supports obsolete SHA1-based ciphersuites

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Broadcom RAID Controller web interface has an insecure default TLS configuration that supports obsolete SHA1-based ciphersuites, which are cryptographically weak and vulnerable to collision attacks, allowing potential man-in-the-middle attackers to compromise encrypted sessions.

MitigationDisable SHA1-based ciphersuites in the RAID controller's TLS configuration and configure the web interface to use only strong, modern cipher suites (e.g., TLS 1.2/1.3 with AES-GCM).

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Raid Controller Web InterfaceApplication
Affected:= 51.12.0-2779

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Broadcom RAID Controller Web Interface installation
    Locate the Broadcom RAID Controller web interface component on the system. This is typically accessed via a web browser to the controller's management IP, or through the server's management interface (like iDRAC, ILO, or similar). Check system inventory or installed software lists for 'Broadcom' or 'RAID Controller' web management components.
    Affected if The web interface component is not found on the system (not affected)
  2. Verify the installed version
    Access the RAID controller's web interface login page or the management console's 'About' or 'System Information' section. Look for the version number displayed. Common locations include a footer on the login page, a 'Support' or 'Diagnostics' section, or the controller's firmware/BIOS version display.
    Affected if Version is exactly 51.12.0-2779 (vulnerable version)
  3. Confirm the web interface is enabled and accessible
    Attempt to reach the RAID controller's web interface via HTTPS (port 443 or the configured management port) from an authorized network. Verify the service is running by checking the controller's management web server status if accessible through CLI or management tools.
    Affected if Web interface is enabled and responds to HTTPS requests (potentially vulnerable)
  4. Inspect TLS configuration for SHA1-based ciphersuites
    Use a TLS scanning tool (such as nmap with ssl-enum-ciphers, testssl.sh, or openssl s_client) to connect to the RAID controller's web interface endpoint. Run a ciphersuite enumeration scan to list all supported cipher suites. Look for any ciphersuite strings containing 'SHA1', 'SHA', or 'MD5' in the supported list.
    Affected if SHA1-based or other weak hash-based ciphersuites (e.g., TLS_RSA_WITH_SHA1, TLS_DHE_RSA_WITH_SHA1) appear in the supported ciphers list
  5. Check if using default TLS configuration
    Review the RAID controller's TLS/SSL configuration settings accessible through the web interface management console (under 'Security', 'SSL/TLS Settings', or 'Network Configuration'). Check whether the ciphersuite configuration is set to 'Default' or 'Auto' rather than a manually specified strong cipher list.
    Affected if Configuration shows default or automatic cipher selection (likely includes vulnerable SHA1 ciphers)

A user is affected if they have the Broadcom RAID Controller Web Interface version 51.12.0-2779 with its web interface enabled and the TLS configuration supports SHA1-based ciphersuites in the default or current cipher list.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable SHA1-based ciphersuites in the RAID controller's TLS configuration and configure the web interface to use only strong, modern cipher suites (e.g., TLS 1.2/1.3 with AES-GCM).

Fix this in Raid Controller Web Interface Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,150
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,440.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-4326 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-4326 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data