CVE-2024-23806
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 · uneditedSensitive data can be extracted from HID iCLASS SE reader configuration cards. This could include credential and device administrator keys.
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 vulnerability allows extraction of sensitive data including credential and device administrator keys from HID iCLASS SE reader configuration cards. An attacker with access to these configuration cards could obtain administrative credentials used to manage the physical access control readers.
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 dataall versionsall versionsCVSS 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/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 if you possess HID Omnikey Secure Elements Reader Configuration CardsInventory your physical access control equipment and documentation to determine if any Omnikey Secure Elements Reader Configuration Cards are deployed in your environmentAffected if Your environment contains these configuration cards and they have not been secured against unauthorized physical access
-
Identify if you possess HID iCLASS SE Reader Configuration CardsInventory your physical access control equipment and documentation to determine if any iCLASS SE Reader Configuration Cards are deployed in your environmentAffected if Your environment contains these configuration cards and they have not been secured against unauthorized physical access
-
Review physical access controls to configuration cardsAudit where configuration cards are stored, who has access to them, and whether they are maintained in a physically secure location with access loggingAffected if Configuration cards are stored in locations accessible to unauthorized personnel or lack access control logs
-
Verify accountability of all configuration cardsConduct a physical count of configuration cards against your inventory records to identify any cards that are lost, missing, or unaccounted forAffected if Any configuration cards cannot be accounted for or are confirmed missing from secure storage
-
Check for signs of unauthorized card access or duplicationReview access logs, security camera footage, or maintenance records that might indicate someone has had physical possession of the cardsAffected if Records show unauthorized access to cards or potential duplication attempts
You are affected if your environment contains HID Omnikey Secure Elements or iCLASS SE Reader Configuration Cards and any of these cards have been accessible to unauthorized individuals, are missing, or cannot be verified as continuously secured.
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 dataOrganizations should rotate all exposed credentials and administrator keys on affected readers, reissue configuration cards with updated security parameters, and review access to configuration cards to prevent unauthorized physical access.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23806 — 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-23806 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