Raid Controller Web InterfaceApplication · Broadcom

CVE-2023-4345

MEDIUM · 6.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 →
71/100
Remediation priority · Elevated
Remotely reachable 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 client-side control bypass leads to unauthorized data access for low privileged user

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

Broadcom RAID Controller web interface contains a client-side control bypass vulnerability that allows authenticated users with low privileges to access data beyond their authorized scope. This type of flaw typically involves tampering with client-side parameters, hidden fields, or session tokens to escalate privileges or access restricted resources.

MitigationApply vendor-provided patches or firmware updates for Broadcom RAID Controllers. If no patch is available, implement additional server-side authorization controls and restrict web interface access to trusted networks or users.

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

CVSS:3.1/AV:N/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. Identify Broadcom RAID Controller Web Interface presence
    Access the RAID controller management interface via its web URL (typically https://<controller-ip> or https://<server-ip>/raid) and verify the product is Broadcom RAID Controller Web Interface. Check the login page or about section for product identification.
    Affected if The product is not a Broadcom RAID Controller Web Interface, the user is not affected by this specific CVE.
  2. Check installed web interface version
    Locate the version information in the web interface (usually in Help > About, System Information, or the footer of the web pages). The exact version must be 51.12.0-2779 to be affected.
    Affected if The installed version is exactly 51.12.0-2779, this specific CVE applies. Versions other than 51.12.0-2779 are not affected by this exact vulnerability.
  3. Verify web interface is accessible and enabled
    Confirm the RAID controller web management interface is reachable and functional. Attempt to access the login page or any authenticated section of the interface.
    Affected if The web interface is not enabled or not accessible, the client-side bypass cannot be exploited.
  4. Confirm low-privilege user account existence
    Check if there are any user accounts with restricted or low-level privileges configured in the RAID controller user management section (typically under User Management, Access Control, or Security settings).
    Affected if No low-privilege users exist (only administrator accounts), the privilege escalation aspect of this vulnerability does not apply.

The environment is affected only if it uses Broadcom RAID Controller Web Interface version 51.12.0-2779 with the web interface enabled and configured with user accounts that have limited privileges.

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

Apply vendor-provided patches or firmware updates for Broadcom RAID Controllers. If no patch is available, implement additional server-side authorization controls and restrict web interface access to trusted networks or users.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-4345 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