dbcve.org
Raid Controller Web InterfaceApplication · Broadcom

CVE-2023-4328

MEDIUM · 5.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 →
57/100
Remediation priority · Elevated
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 to exposure of sensitive data and the keys used for encryption are accessible to any local user on Windows

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 · moderate confidence

The Broadcom RAID Controller web interface contains a vulnerability that allows exposure of sensitive data. The encryption keys used for data protection are stored with insufficient access controls, making them accessible to any local user on Windows systems with basic user privileges.

MitigationRestrict file system permissions on encryption key storage locations to administrators only, or rotate affected encryption keys and ensure proper Windows access control lists are applied to prevent unprivileged local user access.

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/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. Verify Broadcom RAID Controller Web Interface version
    Check installed software version on the Windows system. Use 'Programs and Features' or run 'Get-ItemProperty' in PowerShell for registry entries under HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall looking for Broadcom RAID Controller Web Interface, or check the web interface banner/version page if accessible.
    Affected if The installed version is exactly 51.12.0-2779
  2. Locate encryption key storage directory
    Identify directories where Broadcom RAID Controller stores encryption keys. Common locations include the application installation directory and configuration folders under Program Files or ProgramData. Search for files with names containing 'key', 'encrypt', 'crypto', or similar patterns within the Broadcom application directory tree.
    Affected if Encryption key files exist and are found in accessible storage locations on the system
  3. Check file permissions on key storage files
    Use Windows Explorer right-click properties on identified key files, or run 'icacls <filename>' in Command Prompt to view Access Control Lists. Verify which users and groups have Read or ReadAndExecute permissions.
    Affected if Non-administrator local users (such as standard users or the Users group) have Read access to encryption key files, indicating insufficient access controls
  4. Verify non-privileged user access
    Attempt to access the encryption key files using a standard local user account (non-admin), or simulate this by checking if the Everyone or Users group has access permissions via 'icacls' output.
    Affected if A standard user account without administrative privileges can successfully read or copy encryption key files

A system is affected if Broadcom RAID Controller Web Interface version 51.12.0-2779 is installed and encryption key files are readable by non-administrative local users due to overly permissive file access controls.

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

Restrict file system permissions on encryption key storage locations to administrators only, or rotate affected encryption keys and ensure proper Windows access control lists are applied to prevent unprivileged local user access.

Fix this in Raid Controller Web Interface Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-4328 — 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-4328 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