dbcve.org
WorkcentreHardware / appliance · Xerox

CVE-2006-6473

HIGH · 10.0 CVSS v2.0 Published 2006-12-11
Fix available
A fix is available. Upgrade to after 14.050.02.000 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
Multiple unspecified vulnerabilities in Xerox WorkCentre and WorkCentre Pro before 12.050.03.000, 13.x before 13.050.03.000, and 14.x before 14.050.03.000 have unknown impact and attack vectors, related to (1) an Immediate Image Overwrite (IIO) error message at the Local User Interface (LUI) if overwrite fails, (2) an IIO failure when a Held Job is deleted, and (3) an On Demand Image Overwrite failure when the overwrite is greater than 2 Gb.

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

A detailed technical summary for this CVE is being prepared.

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
WorkcentreHardware / appliance
Affected:<= 13.050.02.000<= 14.050.02.000

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 a release after 14.050.02.000
Vendor patch secunia.com →
Recommended fix High confidence

Upgrade to WorkCentre firmware 13.050.03.000 (for 13.x) or 14.050.03.000 (for 14.x), or 12.050.03.000 (for 12.x)

  1. 1. Identify the current installed version of Xerox WorkCentre or WorkCentre Pro by accessing the machine's front panel or admin interface
  2. 2. If running version 12.x (< 12.050.03.000), 13.x (<= 13.050.02.000), or 14.x (<= 14.050.02.000), the system is vulnerable
  3. 3. Contact Xerox support or access the Xerox website to obtain the appropriate firmware update
  4. 4. Download the firmware version 12.050.03.000 (for 12.x systems), 13.050.03.000 (for 13.x systems), or 14.050.03.000 (for 14.x systems)
  5. 5. Follow Xerox standard firmware upgrade procedures - typically via the CentreWare web interface or local admin console
  6. 6. After upgrade, verify the new firmware version is installed and confirm the Image Overwrite functionality works correctly
  7. 7. Test all three reported issues: IIO error messages, Held Job deletion, and On Demand Image Overwrite for files > 2Gb
Caveat Review Xerox release notes for any changes to Image Overwrite functionality or admin procedures in the new version

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

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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