CVE-2022-1742
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 · uneditedThe tested version of Dominion Voting Systems ImageCast X allows for rebooting into Android Safe Mode, which allows an attacker to directly access the operating system. An attacker could leverage this vulnerability to escalate privileges on a device and/or install malicious code.
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 ImageCast X voting machine allows an attacker to reboot into Android Safe Mode through physical access, bypassing normal operating system controls. Safe Mode provides direct access to the underlying Android OS, enabling privilege escalation and installation of malicious code on the device.
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 versions= 5.5.10.30= 5.5.10.32CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/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 as Dominionvoting Imagecast XLocate the voting machine and verify the manufacturer and model number on the device chassis or system information screen; confirm it is a Dominionvoting Imagecast X unitAffected if The device is confirmed to be a Dominionvoting Imagecast X voting machine
-
Check the installed firmware versionAccess the device system settings or boot information screen to view the firmware version; compare against affected versions 5.5.10.30 and 5.5.10.32, or note that all versions are listed as affectedAffected if The firmware version matches 5.5.10.30 or 5.5.10.32, or any version is installed (all versions affected)
-
Inspect physical access controls to the machineExamine the deployment location to determine whether the device is in a secured area with restricted access; verify that tamper-evident seals or locked enclosures are present and intactAffected if The device is in an unsecured or publicly accessible location without physical barriers preventing unauthorized access
-
Verify Safe Mode boot accessibilityAttempt to power cycle the device and observe whether Android Safe Mode is reachable through standard boot procedures (e.g., pressing hardware button combinations during startup); consult vendor documentation for your specific modelAffected if Safe Mode is accessible through boot sequence without firmware-level restrictions
A user is affected if they have a Dominionvoting Imagecast X device with any firmware version deployed in a location where physical access to initiate a Safe Mode boot is possible.
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 dataRestrict physical access to voting machines to prevent unauthorized boot into Safe Mode; work with vendor to disable or secure Safe Mode functionality through firmware updates and hardened boot configurations.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-1742 — 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-2022-1742 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