CVE-2004-2166
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 · uneditedThe print-from-email feature in the Canon ImageRUNNER (iR) 5000i and C3200 digital printer, when not using IP address range filtering, allows remote attackers to print arbitrary text without authentication via a text/plain email to TCP port 25.
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 confidenceThe Canon ImageRUNNER 5000i and C3200 digital printers have an unauthenticated email printing vulnerability in their print-from-email feature. When IP address range filtering is not enabled, the SMTP service (TCP port 25) accepts and processes any text/plain email and prints its contents without authentication, allowing remote attackers to send arbitrary print jobs.
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 dataall versionsall versionsCVSS 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
- Partial
AV:N/AC:L/Au:N/C:P/I:P/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's web interface or control panel and verify the model number is Canon ImageRUNNER 5000i or Canon ImageRUNNER C3200Affected if Device is either of these two models
-
Verify print-from-email feature is enabledCheck the device settings for the email print (SMTP print) feature - this is typically found in the network settings or remote UI under Email Print or Print from Email configurationAffected if The print-from-email feature is turned on
-
Confirm SMTP service is accessible on port 25Attempt to connect to the device on TCP port 25 using telnet or netcat: telnet <device_ip> 25, or use a network scanner to verify port 25 is open and respondingAffected if Port 25 is open and accepts SMTP connections
-
Check IP address range filtering statusAccess the device's network security settings (typically in Remote UI under Network Settings or Security Settings) and locate IP address filtering/allow list configuration for the email print featureAffected if IP address range filtering is disabled, not configured, or allows unrestricted access (empty or overly broad allow list)
A user is affected if they have a Canon ImageRUNNER 5000i or C3200 with the print-from-email feature enabled, SMTP port 25 exposed, and IP address range filtering either disabled or not properly configured to restrict access to trusted sources.
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 dataEnable and properly configure IP address range filtering on the affected Canon ImageRUNNER devices to restrict the print-from-email feature to trusted IP addresses or network ranges only.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2004-2166 — 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-2004-2166 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