dbcve.org
Mf755cdw FirmwareOperating system · Canon

CVE-2023-6231

CRITICAL · 9.8 CVSS v3.1 Published 2024-02-06
Fix available
A fix is available. Upgrade to after 03.07 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 WSD probe request process of 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 LBP670C Series/Satera MF750C Series firmware v03.07 and earlier sold in Japan. Color imageCLASS LBP674C/Color imageCLASS X LBP1333C/Color imageCLASS MF750C Series/Color imageCLASS X MF1333C Series firmware v03.07 and earlier sold in US. i-SENSYS LBP673Cdw/C1333P/i-SENSYS MF750C Series/C1333i Series firmware v03.07 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 · moderate confidence

A buffer overflow vulnerability exists in the WSD (Web Services on Devices) probe request handling of affected Canon printer firmware versions v03.07 and earlier. An attacker on the adjacent network segment can send a specially crafted WSD probe request to overflow a buffer, potentially causing the device to become unresponsive or enabling arbitrary code execution.

MitigationUpdate affected printer firmware to v03.08 or later. If patching is not immediately possible, isolate printers on a separate VLAN, disable WSD services if not required, and implement network access controls to restrict unauthorized devices from sending WSD probe requests.

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
Mf755cdw FirmwareOperating system
Affected:<= 03.07
Mf753cdw FirmwareOperating system
Affected:<= 03.07
Mf751cdw FirmwareOperating system
Affected:<= 03.07
Lbp674c FirmwareOperating system
Affected:<= 03.07
Lbp672c FirmwareOperating system
Affected:<= 03.07
Lbp671c FirmwareOperating system
Affected:<= 03.07
Mf1238 Ii FirmwareOperating system
Affected:<= 03.07
Mf1333c FirmwareOperating system
Affected:<= 03.07

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 Canon printer model
    Locate the printer on the network or physically inspect the device label to confirm the exact model number (e.g., Mf755cdw, Lbp672c, Mf1333c)
    Affected if The model is one of: Canon Mf755cdw, Mf753cdw, Mf751cdw, Lbp674c, Lbp672c, Lbp671c, Mf1238 Ii, or Mf1333c
  2. Check the installed firmware version
    Access the printer web interface (http://<printer-ip>) and navigate to the firmware or device information page, or use the printer control panel to locate the firmware version in the system settings or maintenance menu
    Affected if The firmware version is 03.07 or any version earlier than 03.07 (e.g., 03.05, 03.00, 02.x)
  3. Verify WSD service status
    Log into the printer web interface and check the network settings or services configuration for Web Services on Devices (WSD) status. WSD is typically listed under Network Settings, Port Settings, or Services. Confirm if WSD discovery or WSD Print is enabled.
    Affected if WSD is enabled and active on the device
  4. Check network accessibility of WSD ports
    Scan the printer IP for open WSD ports using a network scanner or command: nmap -p 3702,80,8080 <printer-ip> or manually test if UDP port 3702 (WS-Discovery) is responsive. Determine if the printer is reachable from network segments other than its own VLAN.
    Affected if The printer WSD ports are exposed to adjacent network segments or untrusted VLANs

You are affected if you have any of the listed Canon models with firmware version 03.07 or earlier, WSD is enabled, and the device is accessible from an adjacent network segment where an attacker could send malicious WSD probe requests.

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

Update affected printer firmware to v03.08 or later. If patching is not immediately possible, isolate printers on a separate VLAN, disable WSD services if not required, and implement network access controls to restrict unauthorized devices from sending WSD probe requests.

Recommended fix Moderate confidence

Firmware version newer than 03.07 (check Canon support for specific latest version for each model)

  1. 1. Identify the exact model number of the Canon printer from the affected series (Satera, Color imageCLASS, or i-SENSYS).
  2. 2. Navigate to the official Canon support website for your region (canon.jp for Japan, usa.canon.com for US, canon-europe.com for Europe).
  3. 3. Enter the model number in the search or product support section.
  4. 4. Locate the firmware download area and check for any firmware version newer than v03.07.
  5. 5. Download the latest firmware version available for the specific model.
  6. 6. Follow Canon's firmware update instructions - typically this involves accessing the printer's web interface or using the Canon firmware update utility.
  7. 7. Apply the firmware update to remediate the buffer overflow vulnerability in the WSD probe request process.
Caveat Standard firmware update risk - ensure stable power during update; review release notes for any functionality changes

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

Fix this in Mf755cdw 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-6231 — 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-6231 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