CVE-2024-47976
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 · uneditedImproper access removal handling in firmware of some Solidigm DC Products may allow an attacker with physical access to gain unauthorized access.
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 confidenceImproper access removal handling in firmware of Solidigm DC Products (data center SSDs) creates a flaw where access control mechanisms fail to properly revoke or remove authorization when triggered, potentially allowing an attacker with physical access to bypass authentication and gain unauthorized data access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Physical
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:P/AC:H/PR:L/UI:N/S:C/C:H/I:H/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 Solidigm DC SSD presenceUse storage management tools (smartctl, storcli, or vendor-specific tools like Solidigm Storage Tool) to enumerate installed SSDs and identify Solidigm DC series models (e.g., Solidigm DC Pxxxx series). Check system inventory or RAID controller logs for Solidigm data center SSD models.Affected if Solidigm DC series SSDs are present in the system
-
Retrieve Solidigm DC SSD firmware versionExecute 'smartctl -a /dev/sdX' or use Solidigm Storage Tool (solidigm-storage-tool) with 'device info' command to query the firmware version of each identified Solidigm DC SSD. Record the firmware revision string.Affected if Firmware version has not been updated to the patched version released by Solidigm for this CVE
-
Verify access control feature statusCheck if ATA Security or TCG (Trusted Computing Group) Opal encryption is enabled on the Solidigm DC SSD using 'smartctl -g security /dev/sdX' or vendor tools. Determine whether password-based authentication or TCG activation is configured.Affected if Access control/encryption features are enabled on the drive and the firmware is unpatched
-
Test access control revocation behaviorIf access control is configured, perform a test of the revocation mechanism: lock the drive using the configured authentication, then attempt to remove/unlock access. Verify through vendor diagnostic tools or ATA commands (SECURITY UNLOCK, SECURITY ERASE PREPARE) whether authorization is properly removed or persists unexpectedly.Affected if Authorization persists after revocation attempt or drive fails to properly clear authentication state
Environment is affected if Solidigm DC SSDs are present with unpatched firmware and access control/encryption features are enabled, allowing potential unauthorized access upon physical attack.
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 dataApply firmware updates provided by Solidigm for affected DC product lines; verify access control revocation functions correctly post-update.
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47976 — 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-2024-47976 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