CVE-2006-1139
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 · uneditedUnspecified vulnerability in the ESS/ Network Controller in Xerox CopyCentre and Xerox WorkCentre Pro, running software 1.001.02.073 or earlier, or 1.001.02.074 before 1.001.02.715, causes the Immediate Image Overwrite feature to fail after a power loss, which could leave data exposed to attack.
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 confidenceThe Xerox CopyCentre and WorkCentre Pro devices with ESS/Network Controller running software versions 1.001.02.073 or earlier, or version 1.001.02.074 prior to 1.001.02.715, have a vulnerability where the Immediate Image Overwrite feature fails to execute properly after a power loss event, potentially leaving sensitive data from previous scan or print jobs exposed on the device storage.
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<= 1.001.02.073>= 1.001.02.074, < 1.001.02.715<= 1.001.02.073>= 1.001.02.074, < 1.001.02.715<= 1.001.02.073>= 1.001.02.074, < 1.001.02.715<= 1.001.02.073>= 1.001.02.074, < 1.001.02.715<= 1.001.02.073>= 1.001.02.074, < 1.001.02.715<= 1.001.02.073>= 1.001.02.074, < 1.001.02.715CVSS 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
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:P/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Xerox device modelCheck the physical device label or access the device web interface (usually via its IP address) to determine if the device is a CopyCentre C65/C75/C90 or WorkCentre Pro 65/75/90Affected if The device model is one of: CopyCentre C65, CopyCentre C75, CopyCentre C90, WorkCentre Pro 65, WorkCentre Pro 75, or WorkCentre Pro 90
-
Check the installed firmware versionAccess the device system information page via the web interface or print a configuration/report page from the device control panel to retrieve the firmware versionAffected if The firmware version is 1.001.02.073 or earlier, OR is 1.001.02.074 through 1.001.02.714 (anything below 1.001.02.715)
-
Determine if Immediate Image Overwrite is enabledAccess the device security or system settings via the web interface or control panel and check the configuration status of the Immediate Image Overwrite featureAffected if The Immediate Image Overwrite feature is turned on or configured on the device
The device is affected if it is a CopyCentre C65/C75/C90 or WorkCentre Pro 65/75/90 with firmware version 1.001.02.073 or earlier, or version 1.001.02.074 through 1.001.02.714, and the Immediate Image Overwrite feature is enabled
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 data1.001.02.715
Upgrade the device firmware to version 1.001.02.715 or later for the 1.001.02.074 branch (or latest available for earlier versions). Consider network isolation of affected devices and ensure power conditioning to minimize unexpected shutdowns.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-1139 — 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-2006-1139 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