Altalink B8045 FirmwareOperating system · Xerox

CVE-2019-18630

HIGH · 7.5 CVSS v3.1 Published 2021-03-04
Fix available
A fix is available. Upgrade to 103.001.010.14010 / 103.002.010.14010 or later.
See remediation →
84/100
Remediation priority · High
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
On Xerox AltaLink B8045/B8055/B8065/B8075/B8090 and C8030/C8035/C8045/C8055/C8070 multifunction printers with software releases before 101.00x.099.28200, portions of the drive containing executable code were not encrypted thus leaving it open to potential cryptographic information disclosure.

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 printers have unencrypted drive partitions containing executable code in software versions prior to 101.00x.099.28200, allowing potential cryptographic information disclosure through drive access.

MitigationUpdate Xerox AltaLink printer firmware to version 101.00x.099.28200 or later to encrypt the drive partitions containing executable code.

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 B8045 FirmwareOperating system
Affected:< 103.008.010.14010
Altalink B8055 FirmwareOperating system
Affected:< 103.008.010.14010
Altalink B8065 FirmwareOperating system
Affected:< 103.008.010.14010
Altalink B8075 FirmwareOperating system
Affected:< 103.008.010.14010
Altalink B8090 FirmwareOperating system
Affected:< 103.008.010.14010
Altalink C8030 FirmwareOperating system
Affected:< 103.001.010.14010
Altalink C8035 FirmwareOperating system
Affected:< 103.001.010.14010
Altalink C8045 FirmwareOperating system
Affected:< 103.002.010.14010

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

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

  1. Identify the AltaLink printer model
    Locate the model number on the front of the device or in the web interface under Device Information. The affected models are B8045, B8055, B8065, B8075, B8090, C8030, C8035, and C8045.
    Affected if The device is one of these eight AltaLink models.
  2. Access the printer web interface
    Open a web browser and enter the printer IP address to access the Xerox Embedded Web Server. Log in with administrator credentials.
    Affected if You can access the web interface to view device information.
  3. Locate the firmware version
    Navigate to the Device Information or General section in the web interface. Look for the Firmware Version or System Software Version field.
    Affected if A firmware version number is displayed.
  4. Compare firmware version to affected ranges
    Match your model and firmware version against these thresholds: B8045/B8055/B8065/B8075/B8090 require 103.008.010.14010 or higher; C8030/C8035 require 103.001.010.14010 or higher; C8045 requires 103.002.010.14010 or higher.
    Affected if Your installed firmware version is LOWER than the required threshold for your specific model.
  5. Verify if unencrypted partitions exist
    This requires physical access or administrative access to check drive encryption status. In the web interface, look under Security or Storage settings for drive encryption or partition status information.
    Affected if Drive encryption is disabled or unencrypted partitions are present.

A user is affected if they have an AltaLink B8045-B8090 or C8030-C8045 model with firmware below the specific threshold for their model, and the drive partitions remain unencrypted.

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
Upgrade available Upgrade to 103.001.010.14010 / 103.002.010.14010 / 103.008.010.14010 or later
Fixed in 103.001.010.14010103.002.010.14010103.008.010.14010
Interim mitigation

Update Xerox AltaLink printer firmware to version 101.00x.099.28200 or later to encrypt the drive partitions containing executable code.

Fix this in Altalink B8045 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-18630 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-18630 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