CVE-2019-10960
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 · uneditedZebra Industrial Printers All Versions, Zebra printers are shipped with unrestricted end-user access to front panel options. If the option to use a passcode to limit the functionality of the front panel is applied, specially crafted packets could be sent over the same network to a port on the printer and the printer will respond with an array of information that includes the front panel passcode for the printer. Once the passcode is retrieved, an attacker must have physical access to the front panel of the printer to enter the passcode to access the full functionality of the front panel.
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 · high confidenceZebra Industrial Printers ship with unrestricted front panel access. When passcode protection is enabled, specially crafted network packets sent to a specific port cause the printer to respond with an array of information that includes the plaintext front panel passcode. An attacker with network access can retrieve the passcode and use physical access to the front panel to gain full functionality.
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 versionsall versionsall versionsall versionsall versionsall 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 printer model and firmware versionAccess the printer's web interface, check the front panel display, or use SNMP/lpd commands to retrieve the model number (Zt610, Zt620, Zt510, Zt410, Zt420, Zt220, Zt230, or 220xi4) and current firmware version.Affected if The printer is any of the following models: Zt610, Zt620, Zt510, Zt410, Zt420, Zt220, Zt230, or 220xi4 with any firmware version.
-
Verify network accessibility to the printerConfirm the printer has an active network IP address and is reachable from your network segment. Use ping or port scanning tools to determine if the printer is accessible over the network.Affected if The printer is network-accessible (has an IP address and responds to network requests).
-
Check if the vulnerable service port is exposedScan the printer's IP address for open ports, particularly the port used by this vulnerability (typically port 9100 for raw print services, though the CVE references a specific vulnerable port). Compare findings against expected baseline ports.Affected if The printer exposes network services that could accept the specially crafted packets described in the CVE.
-
Confirm passcode protection statusAccess the printer front panel menu or web interface settings to check whether front panel passcode protection is currently enabled. Look for passcode/PIN protection settings under Security or Access Control menus.Affected if Front panel passcode protection is enabled on the printer (this is the required condition for the vulnerability to expose the passcode).
A user is affected if they have a vulnerable Zebra printer model (Zt610, Zt620, Zt510, Zt410, Zt420, Zt220, Zt230, or 220xi4) that is network-accessible AND has front panel passcode protection enabled, allowing an attacker on the network to retrieve the plaintext passcode.
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 network access to printers via segmentation or firewall rules; apply vendor firmware updates when available; consider disabling the front panel passcode feature if not required.
- Consultation4.0 h
- Implementation12.0 h
- Testing4.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 $6,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10960 — 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-2019-10960 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