CVE-2019-13168
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 · uneditedSome Xerox printers (such as the Phaser 3320 V53.006.16.000) were affected by a buffer overflow vulnerability in the attributes parser of the IPP service. This would allow an unauthenticated attacker to cause a Denial of Service (DoS) and potentially execute arbitrary code on the 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 buffer overflow vulnerability exists in the attribute parser of the IPP (Internet Printing Protocol) service on certain Xerox printers including the Phaser 3320 (firmware V53.006.16.000). An unauthenticated attacker can exploit this flaw remotely over the network to crash the device (DoS) or potentially achieve arbitrary code execution with elevated privileges on the embedded system.
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= v53.006.16.000CVSS 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 printer modelAccess the printer's web interface, print a configuration page, or check the device label to confirm the model is Xerox Phaser 3320Affected if The device is not a Xerox Phaser 3320, then it is not affected by this specific CVE
-
Check the installed firmware versionVia the printer's web interface under Status or Configuration page, or by printing a test/configuration page. Look for a firmware version field.Affected if The firmware version is exactly v53.006.16.000 - other versions are not affected by this specific CVE
-
Verify IPP service is enabledCheck the printer's web interface for IPP (Internet Printing Protocol) settings, typically found under Network Settings, Ports, or Printing preferences. Confirm IPP is turned on.Affected if IPP is disabled, the vulnerability cannot be exploited even on the affected firmware version
-
Check IPP network exposureDetermine if the printer's IPP port (typically port 631) is accessible from untrusted networks. Check firewall rules, VLAN configuration, and whether the printer is directly internet-facing.Affected if The IPP service is exposed to untrusted networks (such as the public internet), an unauthenticated attacker can reach the vulnerable service
A user is affected only if they have a Xerox Phaser 3320 with firmware version v53.006.16.000 AND IPP is enabled and network-accessible to untrusted parties.
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 dataApply available firmware updates from Xerox; if no patch exists, network segment IPP services behind firewalls or disable IPP exposure to untrusted networks, and consider replacing end-of-life devices.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-13168 — 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-13168 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