CVE-2023-4327
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 · uneditedBroadcom RAID Controller web interface is vulnerable to exposure of sensitive data and the keys used for encryption are accessible to any local user on Linux
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 confidenceThe Broadcom RAID Controller web interface contains a vulnerability that allows local Linux users to access sensitive data, specifically the encryption keys used for data protection. This exposure occurs due to insufficient access controls on the web interface, permitting any local user on the system to retrieve the encryption keys.
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= 51.12.0-2779CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Broadcom RAID Controller Web Interface is presentLocate the RAID controller web interface software on the system. This is typically installed on a management server or the RAID controller appliance itself running a Linux-based OS.Affected if The web interface software is installed and running on the system.
-
Check the installed version of the web interfaceRetrieve the version information of the Broadcom RAID Controller Web Interface using the vendor-provided method (such as the web interface about page, CLI tool, or management software). Compare the version number to 51.12.0-2779.Affected if The installed version is exactly 51.12.0-2779.
-
Verify local user access to web interface endpointsTest whether local unprivileged Linux users can access the web interface URLs that serve encryption key data. Attempt to retrieve the key storage or configuration endpoints accessible through the web interface without authentication restrictions.Affected if Local users can access sensitive web interface endpoints containing encryption keys without proper access controls.
-
Inspect access permissions on key storage locationsExamine file system permissions on the RAID controller configuration and key storage directories. Verify if the web interface process or configuration files storing encryption keys are readable by all local system users.Affected if Encryption keys or key storage files are readable by any local user due to overly permissive file permissions.
A system is affected if it runs Broadcom RAID Controller Web Interface version 51.12.0-2779 and allows local Linux users to access the web interface or its key storage without proper access restrictions.
Generated from the published advisory. Verify against your own configuration.
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 dataRestrict local system access to trusted personnel only, ensure proper file system permissions are applied to the RAID controller configuration and key storage locations, and apply any vendor-provided security updates or patches for the RAID Controller firmware.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-4327 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-4327 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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