CVE-2006-1138
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 web server code 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, allows remote attackers to cause a denial of service (memory corruption) via unknown vectors.
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 confidenceMemory corruption vulnerability in the embedded web server component of Xerox CopyCentre and WorkCentre Pro multifunction printers running software versions 1.001.02.073 or earlier, or unpatched 1.001.02.074, allows remote unauthenticated attackers to cause denial of service via malformed HTTP requests.
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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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.
-
Confirm device modelAccess the device web interface or check the physical label to identify if the device is a Xerox CopyCentre C65/C75/C90 or WorkCentre Pro 65/75/90Affected if Device is not one of the listed models, then it is not affected by this CVE
-
Verify embedded web server is enabledAttempt to access the device web interface at the device IP address using HTTP (port 80) or HTTPS (port 443). If the web page loads, the embedded web server is enabled.Affected if Web server is disabled or not accessible, then the attack surface does not exist for this CVE
-
Retrieve firmware versionLog into the web interface and navigate to the Properties or System section to view the firmware version. Alternatively, check the version displayed on the device control panel or via SNMP query.Affected if Unable to determine firmware version, version detection is inconclusive
-
Compare firmware version to vulnerable rangesCompare the installed firmware version to the affected ranges: version <= 1.001.02.073 OR version >= 1.001.02.074 AND < 1.001.02.715Affected if Version falls within <= 1.001.02.073 or within 1.001.02.074 to 1.001.02.714, then the device is vulnerable
The device is affected if it is a Xerox CopyCentre C65/C75/C90 or WorkCentre Pro 65/75/90 with the embedded web server enabled and firmware version in the range 1.001.02.073 or earlier, or 1.001.02.074 through 1.001.02.714.
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
Apply vendor firmware patch 1.001.02.715 or later to affected devices; restrict network access to MFP web interfaces using firewall rules or VLAN segmentation as an interim control.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-1138 — 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-1138 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