dbcve.org
Altalink C8030 FirmwareOperating system · Xerox

CVE-2018-17172

CRITICAL · 9.8 CVSS v3.0 Published 2019-01-03
Fix available
A fix is available. Upgrade to 100.001.028.05200 / 100.002.028.05200 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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 web application on Xerox AltaLink B80xx before 100.008.028.05200, C8030/C8035 before 100.001.028.05200, C8045/C8055 before 100.002.028.05200, and C8070 before 100.003.028.05200 allows unauthenticated command injection.

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 confidence

The Xerox AltaLink multifunction printer web application contains an unauthenticated command injection vulnerability, allowing remote attackers to execute arbitrary operating system commands without any authentication credentials. This critical flaw affects multiple AltaLink models running firmware versions prior to the specified patched releases.

MitigationApply the appropriate vendor firmware update (100.008.028.05200 for B80xx, 100.001.028.05200 for C8030/C8035, 100.002.028.05200 for C8045/C8055, or 100.003.028.05200 for C8070) to remediate the command injection vulnerability.

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
Altalink C8030 FirmwareOperating system
Affected:< 100.001.028.05200
Altalink C8035 FirmwareOperating system
Affected:< 100.001.028.05200
Altalink C8045 FirmwareOperating system
Affected:< 100.002.028.05200
Altalink C8055 FirmwareOperating system
Affected:< 100.002.028.05200
Altalink C8070 FirmwareOperating system
Affected:< 100.003.028.05200
Altalink B8045 FirmwareOperating system
Affected:< 100.008.028.05200
Altalink B8055 FirmwareOperating system
Affected:< 100.008.028.05200
Altalink B8065 FirmwareOperating system
Affected:< 100.008.028.05200

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

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

  1. Access the printer web interface
    Open a web browser and navigate to the IP address of the AltaLink device. Look for a Device Information, About, or Version section typically found under Settings or the gear icon.
    Affected if The web interface is accessible without authentication.
  2. Identify the exact model number
    Locate the model name (such as C8030, C8035, C8045, C8055, C8070, B8045, B8055, or B8065) displayed in the web interface or on the physical device label.
    Affected if The model is one of the eight AltaLink models listed in the affected products.
  3. Find the installed firmware version
    In the web interface, navigate to the firmware or version information page. The version typically appears as a numeric string such as 100.001.xx.xxxxx. Record the full firmware version number.
    Affected if The firmware version is displayed and can be compared against the patched versions.
  4. Compare firmware version to patched releases
    Check your installed version against these thresholds: C8030/C8035 need 100.001.028.05200 or higher; C8045/C8055 need 100.002.028.05200 or higher; C8070 needs 100.003.028.05200 or higher; B8045/B8055/B8065 need 100.008.028.05200 or higher.
    Affected if Your installed version is lower than the threshold for your specific model.

You are affected if your AltaLink model is one of the eight listed and the web interface is accessible with a firmware version below the patched threshold for that model.

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.

dbcve · scoped
Upgrade available Upgrade to 100.001.028.05200 / 100.002.028.05200 / 100.003.028.05200 or later
Fixed in 100.001.028.05200100.002.028.05200100.003.028.05200
Interim mitigation

Apply the appropriate vendor firmware update (100.008.028.05200 for B80xx, 100.001.028.05200 for C8030/C8035, 100.002.028.05200 for C8045/C8055, or 100.003.028.05200 for C8070) to remediate the command injection vulnerability.

Recommended fix High confidence

Firmware 100.001.028.05200 (C8030/C8035), 100.002.028.05200 (C8045/C8055), 100.003.028.05200 (C8070), or 100.008.028.05200 (B80xx)

  1. Identify the specific AltaLink model (C8030, C8035, C8045, C8055, C8070, B8045, B8055, or B8065) from the device
  2. Check the current firmware version in the device web interface under Maintenance or System settings
  3. Download the firmware update from Xerox support portal (securitydocs.business.xerox.com or Xerox.com support) matching your specific model
  4. Upload and install the firmware update via the device web interface or Xerox CentreWare software
  5. After reboot, verify the firmware version shows the fixed release: 100.001.028.05200 (C8030/C8035), 100.002.028.05200 (C8045/C8055), 100.003.028.05200 (C8070), or 100.008.028.05200 (B80xx)
Caveat Review Xerox release notes for any functionality changes; firmware updates on multifunction devices may require reconfiguration of network settings or stored address books

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Altalink C8030 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-17172 — 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-2018-17172 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