CVE-2023-33222
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 · uneditedWhen handling contactless cards, usage of a specific function to get additional information from the card which doesn't check the boundary on the data received while reading. This allows a stack-based buffer overflow that could lead to a potential Remote Code Execution on the targeted device
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 confidenceA stack-based buffer overflow vulnerability exists in the contactless card handling functionality of the affected device. The vulnerability stems from a specific function that retrieves additional information from cards without performing proper boundary checks on the incoming data, allowing an attacker to overflow the stack buffer and potentially execute arbitrary code remotely.
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< 4.15.5< 4.15.5< 4.15.5< 4.15.5< 2.12.2< 2.12.2< 2.12.2< 1.2.7CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 device modelLocate the physical device or check the device inventory/management interface to determine the exact model (Sigma Lite, Sigma Lite+, Sigma Extreme, Sigma Wide, Morphowave Compact, Morphowave Xp, Visionpass, or Morphowave Sp)Affected if The device is any of these eight models listed in the affected products
-
Check the installed firmware versionAccess the device administration interface or use the vendor management tool to retrieve the current firmware version. Compare it against the affected version thresholds: Sigma series below 4.15.5, Morphowave Compact/Xp and Visionpass below 2.12.2, Morphowave Sp below 1.2.7Affected if The firmware version is lower than the threshold for your specific model
-
Verify if contactless card reading is enabledCheck the device configuration settings in the admin interface to see if the contactless card reader module is enabled and configured for useAffected if Contactless card reading is enabled and the device reads cards without additional authentication
You are affected if you own one of the eight listed Idemia device models, your firmware version is below the specified threshold, and contactless card reading functionality is enabled on the device.
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.
dbcve · scoped1.2.72.12.24.15.5
Implement proper bounds checking on all data received from contactless cards before copying into fixed-size buffers. Apply any vendor-supplied patches or firmware updates that address this boundary validation issue.
Sigma Lite/Lite+/Extreme/Wide: upgrade to firmware 4.15.5 | Morphowave Compact/Xp/Visionpass: upgrade to firmware 2.12.2 | Morphowave Sp: upgrade to firmware 1.2.7
- Identify the exact model of the affected device (Sigma Lite, Sigma Lite+, Sigma Extreme, Sigma Wide, Morphowave Compact, Morphowave Xp, Visionpass, or Morphowave Sp)
- Access the device management interface or control panel
- Check the current firmware version to confirm it is vulnerable (Sigma products: < 4.15.5, Morphowave Compact/Xp/Visionpass: < 2.12.2, Morphowave Sp: < 1.2.7)
- Obtain the corresponding firmware update from IDEMIA's official support portal or through your authorized IDEMIA channel
- Follow IDEMIA's standard firmware update procedure for the specific device model (typically via device management software or web interface)
- After updating, verify the firmware version matches the fixed release (Sigma: 4.15.5, Morphowave Compact/Xp/Visionpass: 2.12.2, Morphowave Sp: 1.2.7)
- Test that contactless card reading functionality operates normally
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-33222 — 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-33222 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