CVE-2023-4343
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 due to exposure of sensitive password information in the URL as a URL search parameter
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 confidenceThe Broadcom RAID Controller web interface transmits sensitive password credentials as URL search parameters, exposing them in browser history, server logs, proxy logs, and referrer headers. This is a sensitive information disclosure vulnerability where authentication credentials are improperly handled.
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 the RAID controller management interface. This is typically accessed via a web browser to the IP address or hostname of the RAID controller. Note the web application version displayed in the interface (often in an About or System Information page).Affected if The installed version is exactly 51.12.0-2779
-
Review server or appliance logs for URL parametersAccess logs from the server or appliance hosting the Broadcom RAID Controller Web Interface. Search log entries for HTTP requests containing '?' followed by credential-related parameter names such as 'password', 'pwd', 'passwd', or 'cred' in the URL query string.Affected if Log entries show passwords or credentials appearing as URL query parameters (e.g., ?password=VALUE)
-
Inspect proxy or reverse proxy logsIf network traffic passes through a proxy or reverse proxy before reaching the RAID controller web interface, examine those proxy logs for requests targeting the RAID controller.Affected if Proxy logs contain full URLs with credentials exposed in the query string portion
-
Examine referrer header logsCheck web server access logs, firewall logs, or intrusion detection system logs for HTTP referrer headers originating from the RAID controller web interface.Affected if Referrer URLs contain credential strings in the URL parameters
-
Verify credential transmission methodUse a browser developer tool or network capture to observe the actual HTTP request when logging into the RAID Controller web interface. Inspect the Request URL to determine if credentials appear as URL parameters rather than in the request body.Affected if Login credentials are transmitted as URL query parameters instead of in the POST request body
The environment is affected if the Broadcom RAID Controller Web Interface version is exactly 51.12.0-2779 AND credentials are observed being transmitted via URL parameters rather than POST body.
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 dataModify the web interface to transmit credentials via POST request body instead of URL parameters. Rotate any exposed credentials and flush existing logs that may contain the exposed passwords.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2023-4343 — 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-4343 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