CVE-2023-4335
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 server (nginx) is serving private server-side files without any authentication 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's embedded nginx web server is misconfigured or has a path traversal vulnerability allowing unauthenticated attackers to access private server-side files. This information disclosure affects Linux deployments and can expose sensitive configuration or system files.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Broadcom RAID Controller Web Interface installationLocate and verify the presence of the Broadcom RAID Controller web interface component on your system. This is typically accessible via a web browser on ports 80, 443, or a custom management port used by Broadcom RAID controllers.Affected if The web interface is installed and accessible on the system
-
Check installed version numberAccess the web interface or check system packages to determine the exact version of the Broadcom RAID Controller Web Interface. Look for version 51.12.0-2779 specifically.Affected if The installed version matches exactly 51.12.0-2779
-
Confirm Linux deploymentDetermine the operating system hosting the RAID controller web interface. Check if the system is running a Linux-based OS.Affected if The affected web interface is running on a Linux operating system
-
Inspect nginx configuration for path traversal exposureExamine the nginx configuration files used by the Broadcom RAID Controller web server. Look for location blocks that may allow directory traversal outside the intended web root, particularly accessing paths like /../ or absolute paths to sensitive directories.Affected if nginx configuration permits unauthenticated access to files outside the web root via path traversal sequences
-
Verify authentication requirements for file endpointsTest whether the web interface requires authentication when attempting to access what should be private configuration files or system files through the nginx server. Attempt requests to internal paths without credentials.Affected if Unauthenticated access to private files or configuration is possible through the web interface
Your environment is affected if you are running the Broadcom RAID Controller Web Interface version 51.12.0-2779 on Linux with the embedded nginx server allowing unauthenticated path traversal access to private files.
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 nginx configuration to block unauthorized access to private directories, apply any available Broadcom patches, and verify that authentication is required for all sensitive file endpoints.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-4335 — 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-4335 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