dbcve.org
Imagecast XOperating system · Dominionvoting

CVE-2022-1745

MEDIUM · 6.8 CVSS v3.1 Published 2022-06-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
The authentication mechanism used by technicians on the tested version of Dominion Voting Systems ImageCast X is susceptible to forgery. An attacker with physical access may use this to gain administrative privileges on a device and install malicious code or perform arbitrary administrative actions.

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 confidence

The ImageCast X voting system uses a technician authentication mechanism that can be forged by an attacker with physical access. This allows the attacker to bypass authentication and gain full administrative privileges on the device, enabling installation of malicious code or execution of arbitrary administrative actions.

MitigationReplace the vulnerable authentication mechanism with a cryptographically secure alternative (e.g., proper certificate-based or hardware token authentication). Implement code signing and integrity verification for all firmware/software. Ensure physical security controls are in place and consider hardware root-of-trust for boot verification.

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
Imagecast XOperating system
Affected:all versions= 5.5.10.30= 5.5.10.32

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Inspect the physical voting device or system inventory to confirm it is a Dominion Voting ImageCast X unit. Check device labeling, serial number documentation, or system configuration files for the model identifier.
    Affected if The device is a Dominion Voting ImageCast X voting system.
  2. Determine the installed firmware version
    Access the device's system information menu, boot logs, or firmware version file. On the ImageCast X, this is typically viewable through the technician interface or by examining the firmware package metadata if accessible via maintenance port.
    Affected if The firmware version matches 5.5.10.30 or 5.5.10.32, or is any version prior to patching (the vulnerability affects all versions).
  3. Verify technician authentication is in use
    Check if the technician authentication mechanism is enabled on the device. Examine the authentication configuration settings accessible via the technician or admin interface, looking for any authentication bypass or privilege escalation settings related to physical maintenance access.
    Affected if Technician authentication mechanism is configured and accessible, as this is the component with the forgeable authentication flaw.
  4. Inspect physical access controls
    Evaluate whether the device is secured against physical tampering. Check for presence of tamper-evident seals, locked chassis, secure mounting, and restricted access to maintenance ports or authentication interfaces.
    Affected if Physical access to the device or its maintenance interfaces is not adequately controlled, allowing an attacker to reach the authentication mechanism.
  5. Review authentication logs for bypass attempts
    Examine system event logs, authentication logs, or audit trails for any successful or attempted technician mode access that may indicate exploitation of the forged authentication vulnerability.
    Affected if There are unexplained technician authentication events or privilege escalation events in the logs.

A user is affected if they operate a Dominion Voting ImageCast X device where the technician authentication mechanism is accessible and physical security controls are insufficient, allowing an attacker with physical access to forge authentication and gain administrative privileges.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace the vulnerable authentication mechanism with a cryptographically secure alternative (e.g., proper certificate-based or hardware token authentication). Implement code signing and integrity verification for all firmware/software. Ensure physical security controls are in place and consider hardware root-of-trust for boot verification.

Fix this in Imagecast X Scoped from the published advisory
  • Consultation12.0 h
  • Implementation40.0 h
  • Testing24.0 h
  • Review / QA16.0 h
92.0 hours of engineering $16,080
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $25,728.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-1745 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-1745 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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