dbcve.org
Mf642cdw FirmwareOperating system · Canon

CVE-2023-0859

MEDIUM · 5.3 CVSS v3.1 Published 2023-05-11
Fix available
A fix is available. Upgrade to after 11.04 or later.
See remediation →
62/100
Remediation priority · Elevated
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
Arbitrary Files can be installed in the Setting Data Import function of Office / Small Office Multifunction Printers and Laser Printers(*). *: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

The Setting Data Import function in affected Canon Satera, Color imageCLASS, and i-SENSYS multifunction printers and laser printers allows installation of arbitrary files due to insufficient validation of imported configuration data. This could allow an attacker to overwrite system files, inject malicious code, or modify device configuration by importing specially crafted data files through the legitimate import feature.

MitigationUpdate the device firmware to a version later than Ver.11.04. If immediate updating is not possible, restrict network access to the printer's administrative interfaces and disable the Setting Data Import function if possible.

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
None
Integrity
Low
Availability
None

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

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
    Check the product label on the device or access the printer's web interface/status page to confirm the exact model number (e.g., MF642cdw, MF644cdw, MF741cdw, MF743cdw, MF745cdw, LBP621c, LBP622c, or LBP661c)
    Affected if The model is one of the eight affected Canon models listed in the CVE
  2. Check the installed firmware version
    Access the printer's web interface (usually via the device's IP address) and navigate to the Device Information or Firmware Update section to view the current firmware version, or check via the printer's control panel under Settings or Device Information
    Affected if The firmware version is 11.04 or lower (any version <= 11.04)
  3. Locate the Setting Data Import function
    Access the printer's web interface and look for settings related to data import/export, configuration backup/restore, or setting import functionality (often found under Settings, Maintenance, or Device Management sections)
    Affected if The Setting Data Import feature is present and accessible on the device
  4. Verify if the Setting Data Import function is enabled
    Check the configuration or settings page for the data import feature to determine whether it is currently enabled or available for use
    Affected if The Setting Data Import function is enabled and can be accessed by an attacker on the network

You are affected if your Canon printer model matches one of the eight listed models AND your firmware version is 11.04 or lower AND the Setting Data Import function is accessible/enabled on your device.

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 the device firmware to a version later than Ver.11.04. If immediate updating is not possible, restrict network access to the printer's administrative interfaces and disable the Setting Data Import function if possible.

Recommended fix High confidence

Canon firmware version > 11.04 (latest available version from Canon support)

  1. Identify your specific Canon printer model from the affected list (Mf642cdw, Mf644cdw, Mf741cdw, Mf743cdw, Mf745cdw, Lbp621c, Lbp622c, Lbp661c or regional variants)
  2. Navigate to the official Canon support website for your region (canon.jp, www.usa.canon.com, or www.canon-europe.com depending on your location)
  3. Locate the firmware download section for your specific printer model
  4. Download the latest firmware version available (must be version higher than 11.04)
  5. Follow Canon's firmware update instructions typically found in the support documentation or user's manual
  6. Connect the printer to a computer via USB or network as directed
  7. Run the firmware update utility and ensure uninterrupted power during the update process
  8. Verify the firmware has been updated by checking the version in the printer's control panel or web interface
Caveat Firmware updates may reset some device settings to factory defaults; backup configuration if possible before updating

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
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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