dbcve.org
Mf642cdw FirmwareOperating system · Canon

CVE-2023-0855

CRITICAL · 9.8 CVSS v3.1 Published 2023-05-11
Fix available
A fix is available. Upgrade to after 11.04 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Buffer overflow in IPP number-up attribute process of Office / Small Office Multifunction Printers and Laser Printers(*) which may allow an attacker on the network segment to trigger the affected product being unresponsive or to execute arbitrary code. *:Satera LBP660C Series/LBP620C Series/MF740C Series/MF640C Series firmware Ver.11.04 and earlier sold in Japan. Color imageCLASS LBP660C Series/LBP 620C Series/X LBP1127C/MF740C Series/MF640C Series/X MF1127C firmware Ver.11.04 and earlier sold in US. i-SENSYS LBP660C Series/LBP620C Series/MF740C Series/MF640C Series, C1127P, C1127iF, C1127i firmware Ver.11.04 and earlier sold in Europe.

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 confidence

Buffer overflow vulnerability in the IPP (Internet Printing Protocol) number-up attribute processing in Canon Satera, Color imageCLASS, and i-SENSYS multifunction printers and laser printers. An attacker on the same network segment can send specially crafted IPP requests to trigger the buffer overflow, potentially causing denial of service or arbitrary code execution.

MitigationUpdate affected Canon printer firmware to a version newer than 11.04. If immediate patching is not feasible, restrict network access to printer IPP services via firewall or network segmentation to prevent unauthorized attackers from reaching the vulnerability.

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
Mf642cdw FirmwareOperating system
Affected:<= 11.04
Mf644cdw FirmwareOperating system
Affected:<= 11.04
Mf741cdw FirmwareOperating system
Affected:<= 11.04
Mf743cdw FirmwareOperating system
Affected:<= 11.04
Mf745cdw FirmwareOperating system
Affected:<= 11.04
Lbp621c FirmwareOperating system
Affected:<= 11.04
Lbp622c FirmwareOperating system
Affected:<= 11.04
Lbp661c FirmwareOperating system
Affected:<= 11.04

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the printer model
    Access the printer's web interface or check the device label to confirm the exact model number (e.g., MF642cdw, MF644cdw, MF741cdw, MF743cdw, MF745cdw, LBp621c, LBp622c, LBp661c).
    Affected if The printer model matches one of the affected models listed in the CVE.
  2. Check the installed firmware version
    Log into the printer web interface and navigate to the Firmware or Device Information section. Compare the firmware version to 11.04. If the version shows as 11.04 or lower, or if the version cannot be determined, treat the device as potentially affected.
    Affected if The firmware version is 11.04 or lower, or the version cannot be verified.
  3. Verify IPP service is enabled
    Access the printer web interface and check the IPP/LPD/Printing service settings. Confirm whether IPP (Internet Printing Protocol) is turned on. Typically found under Network Settings, Printing Settings, or Services.
    Affected if IPP is enabled on the device.
  4. Confirm IPP port accessibility
    From a system on the network, attempt to reach the printer IPP port (default is 631/TCP). Use a command like 'nc -zv <printer-ip> 631' or 'telnet <printer-ip> 631'. If the connection succeeds, the IPP service is exposed.
    Affected if Port 631/TCP is open and reachable from network segments where untrusted users operate.
  5. Review IPP number-up configuration exposure
    If IPP is enabled, verify whether the 'number-up' attribute can be set via IPP requests. This is typically a standard IPP attribute. An exposed IPP service accepting arbitrary job attributes indicates potential exposure to this vulnerability.
    Affected if The IPP service accepts print jobs with custom attributes from network clients.

A user is affected if their printer model is one of the eight listed Canon models, the firmware is version 11.04 or lower, and the IPP service is enabled and accessible on the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 11.04
Interim mitigation

Update affected Canon printer firmware to a version newer than 11.04. If immediate patching is not feasible, restrict network access to printer IPP services via firewall or network segmentation to prevent unauthorized attackers from reaching the vulnerability.

Recommended fix Moderate confidence

Firmware version newer than 11.04 (contact Canon for exact fixed version)

  1. Contact Canon support or visit the official Canon support website (canon.com, canon-europe.com, or canon.jp) for your specific printer model
  2. Locate the firmware download section for your affected printer model (Satera LBP660C/620C, MF740C/640C, Color imageCLASS, or i-SENSYS series)
  3. Download the latest firmware version available for your device
  4. Follow Canon's provided firmware update instructions, typically involving connecting the printer via USB or network and using the provided update utility
  5. After updating, verify the firmware version has changed from 11.04 to a newer version
  6. Restart the printer to ensure the update is fully applied
Caveat Firmware updates may reset printer settings to defaults; record current configuration before updating

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

Fix this in Mf642cdw Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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