CVE-2023-4333
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 doesn’t enforce SSL cipher ordering by server
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 does not enforce SSL cipher ordering by the server, potentially allowing weaker or insecure cipher suites to be negotiated during SSL/TLS connections. This could permit downgrade attacks or use of deprecated cryptographic algorithms.
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 the RAID Controller Web Interface versionLog into the RAID Controller web interface and navigate to the About or Controller Information section. Alternatively, use the Broadcom CLI tool (storcli or perccli) with command: storcli /c0 show all or perccli /c0 show allAffected if The version displayed is exactly 51.12.0-2779
-
Confirm the web interface is SSL/TLS enabledAccess the RAID Controller web interface URL over HTTPS (port 443 or 8443 typically). Verify the connection uses SSL/TLS by checking the browser lock icon and certificate detailsAffected if The web interface accepts HTTPS connections and presents a valid SSL/TLS certificate
-
Test accepted cipher suitesUse nmap with SSL enumeration: nmap --script ssl-enum-ciphers -p 443 <controller-ip> or openssl s_client -connect <controller-ip>:443 -cipher 'aNULL' to test if weak/null ciphers are acceptedAffected if Weak cipher suites (such as NULL, export-grade, or known-vulnerable ciphers) are listed as accepted or connection succeeds with these ciphers
-
Check for legacy protocol supportTest SSLv3 and TLS 1.0/1.1 support: openssl s_client -connect <controller-ip>:443 -ssl3 or -tls1 or -tls1_1. Check if connection succeeds with these older protocolsAffected if The server accepts connections using SSLv3, TLS 1.0, or TLS 1.1 protocols
The environment is affected if the RAID Controller Web Interface version is exactly 51.12.0-2779 and weak cipher suites or legacy TLS protocols are accepted during SSL/TLS negotiation.
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 dataConfigure the RAID Controller web interface to enforce server-defined strong SSL cipher ordering, disabling weak or medium-strength ciphers and restricting to modern TLS protocols.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-4333 — 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-4333 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