CVE-2008-0303
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 FTP print feature in multiple Canon printers, including imageRUNNER and imagePRESS, allow remote attackers to use the server as an inadvertent proxy via a modified PORT command, aka FTP bounce.
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 and imagePRESS printers with FTP print feature allow remote attackers to use the device as an inadvertent proxy via a modified PORT command in the FTP protocol. This is a classic FTP bounce attack where the printer's data connections can be redirected to arbitrary target systems by specifying a different IP address and port in the PORT command, enabling attackers to bypass network restrictions or scan internal networks through the compromised device.
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= lbp3360= lbp3460= lbp5360= c1= 85plus= 105plus= 2230= 2270= 2570c= 2570ci= 2870= 3025= 3025n= 3035= 3035n= 3045all versionsall versionsall versionsall 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
- None
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/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.
-
Identify Canon printer models on the networkScan network for Canon devices or review asset inventory. Look for device hostnames, MAC OUI (Canon), or HTTP management interfaces with Canon branding. Models to match: I-Sensys LBP3360/3460/5360, ImagePRESS C1, imageRUNNER 85plus/105plus/2230/2270/2570c/2570ci/2870/3025/3025n/3035/3035n/3045/2620/5000i/5020/6870/8500.Affected if Any Canon printer from the affected model list is present on the network.
-
Determine if FTP print feature is enabledAccess the printer web interface (HTTP/HTTPS) or print configuration page. Navigate to Network Settings or Print Service settings. Look for FTP Print, FTP Server, or FTP Publishing options and check if enabled. Alternatively, attempt an FTP connection to the device on port 21.Affected if FTP print feature is enabled on the Canon device.
-
Verify FTP service accessibilityFrom an external or untrusted network segment, attempt to connect to the printer IP on port 21 using FTP. Check if the device accepts FTP connections. Review firewall rules to determine if port 21 is open to the printer from non-trusted networks.Affected if Port 21/FTP is reachable from untrusted or internet-facing network segments.
-
Review FTP logs for suspicious activityIf the printer provides FTP logs or the network has FTP traffic captures, look for unusual PORT commands with external IP addresses not belonging to the local network. This indicates potential proxy/bounce attack usage.Affected if FTP logs show PORT commands directing data connections to external IP addresses.
A user is affected if they have any of the listed Canon printer models with the FTP print feature enabled and that FTP service is accessible from untrusted networks.
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 dataDisable the FTP print feature on affected Canon devices if not business-critical, or apply vendor firmware updates if available. Implement network segmentation and firewall rules to restrict inbound FTP access to trusted sources only.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-0303 — 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-2008-0303 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