CVE-2019-10880
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 · uneditedWithin multiple XEROX products a vulnerability allows remote command execution on the Linux system, as the "nobody" user through a crafted "HTTP" request (OS Command Injection vulnerability in the HTTP interface). Depending upon configuration authentication may not be necessary.
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 confidenceThis is an OS command injection vulnerability in the HTTP interface of multiple Xerox products running Linux. An attacker can send a crafted HTTP request that executes arbitrary system commands on the device with 'nobody' user privileges. The critical CVSS score of 9.8 and note that authentication may not be required makes this highly exploitable.
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< 072.161.009.07200< 072.161.009.07200< 072.180.009.07200< 072.180.009.07200< 072.180.009.07200CVSS 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.0/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 Xerox Colorqube modelAccess the device web interface or check the device label to confirm the exact model number (8700, 8900, 9301, 9302, or 9303)Affected if The device is a Xerox Colorqube 8700, 8900, 9301, 9302, or 9303
-
Check the installed firmware versionLog into the device web interface and navigate to the System or Support section to view the firmware version, or access the device via SNMP or the front panel to retrieve the firmware versionAffected if The firmware version is below 072.161.009.07200 for 8700/8900 models, or below 072.180.009.07200 for 9301/9302/9303 models
-
Verify the HTTP management interface is enabledAttempt to access the device HTTP interface by browsing to the device IP address on port 80 or 443, or check the device network configuration settingsAffected if The HTTP management interface is accessible over the network (port 80 or 443 responds)
You are affected if you have a Xerox Colorqube 8700, 8900, 9301, 9302, or 9303 device with firmware below the respective threshold versions AND the HTTP management interface is network-accessible.
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 · scoped072.161.009.07200072.180.009.07200
Apply vendor-supplied patches for affected Xerox products. If patches are unavailable, restrict network access to the HTTP management interface, disable it if unnecessary, or implement network segmentation to limit exposure.
Xerox Colorqube 8700/8900: Firmware 072.161.009.07200 or later; Xerox Colorqube 9301/9302/9303: Firmware 072.180.009.07200 or later
- 1. Identify the exact Colorqube model (8700, 8900, 9301, 9302, or 9303) in your environment
- 2. Check the current firmware version of the device through its admin interface or console
- 3. Navigate to the official Xerox support website or the security documentation portal at securitydocs.business.xerox.com
- 4. Download the corresponding firmware update: For 8700/8900 use version 072.161.009.07200 or later; For 9301/9302/9303 use version 072.180.009.07200 or later
- 5. Apply the firmware update through the device's web interface or management console following Xerox's documented upgrade procedure
- 6. After upgrade, verify the new firmware version is installed and the HTTP interface is functional
- 7. Confirm the vulnerability is remediated by reviewing release notes or applying a post-upgrade security scan
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10880 — 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-10880 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