dbcve.org
Mf642cdw FirmwareOperating system · Canon

CVE-2023-0851

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 CPCA Resource Download 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

A buffer overflow vulnerability exists in the CPCA Resource Download process of Canon Satera, Color imageCLASS, and i-SENSYS multifunction printers and laser printers running firmware version 11.04 and earlier. An unauthenticated attacker on the same network segment can exploit this flaw to either cause the device to become unresponsive (denial of service) or potentially execute arbitrary code with elevated privileges.

MitigationUpdate Canon printer firmware to a version newer than 11.04. As an interim measure, implement network segmentation to isolate printers from untrusted network segments and restrict access to the CPCA service to only authorized management systems.

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 printer model
    Check the printer's web interface, physical label, or printed configuration page to confirm the exact model number (e.g., Mf642cdw, Mf745cdw, Lbp622c)
    Affected if The model is one of the affected models: Mf642cdw, Mf644cdw, Mf741cdw, Mf743cdw, Mf745cdw, Lbp621c, Lbp622c, or Lbp661c
  2. Check installed firmware version
    Access the printer's web interface (remote UI) under Settings or Maintenance, or print a configuration page from the device control panel. Look for the firmware version displayed.
    Affected if The firmware version is 11.04 or earlier
  3. Verify CPCA service exposure
    Check the printer's network settings or service list in the web interface to confirm whether the CPCA (Canon PRINT Business) service is enabled and accessible on the network
    Affected if CPCA service is enabled and accessible from the network segment where untrusted users reside
  4. Assess network accessibility
    Scan the network to confirm whether the printer's HTTP/HTTPS ports (typically 80/443) or CPCA service ports are reachable from network segments containing untrusted users
    Affected if The printer is reachable from an untrusted or guest network segment without firewall restrictions

You are affected if your Canon printer model matches one of the listed models, the firmware version is 11.04 or earlier, and the CPCA service is network-accessible from an untrusted segment.

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 Canon printer firmware to a version newer than 11.04. As an interim measure, implement network segmentation to isolate printers from untrusted network segments and restrict access to the CPCA service to only authorized management systems.

Recommended fix Moderate confidence

Firmware version > 11.04 (check Canon support site for exact version number)

  1. 1. Identify the exact Canon printer model from the affected product list (Mf642cdw, Mf644cdw, Mf741cdw, Mf743cdw, Mf745cdw, Lbp621c, Lbp622c, Lbp661c)
  2. 2. Access the Canon support website for your region (canon.jp, canon-europe.com, or usa.canon.com depending on purchase location)
  3. 3. Navigate to the drivers and downloads section for your specific printer model
  4. 4. Look for firmware updates beyond version 11.04
  5. 5. Download the firmware update file from Canon's official website
  6. 6. Follow Canon's firmware update instructions (typically via the printer's web interface or USB connection)
  7. 7. Verify the firmware has been updated to a version newer than 11.04
Caveat firmware updates may temporarily interrupt printer operation; ensure power is maintained during update process

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

Fix this in Mf642cdw Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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