dbcve.org
Mf755cdw FirmwareOperating system · Canon

CVE-2023-6233

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 SLP attribute 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 SLP (Service Location Protocol) attribute request processing of Canon Office Multifunction Printers and Laser Printers. An attacker on the same network segment can send specially crafted SLP requests to trigger the buffer overflow, potentially causing the device to become unresponsive or allowing arbitrary code execution.

MitigationIsolate affected printers in a dedicated network segment with restricted access, and apply firmware version v03.08 or later when released by Canon to address this 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
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 device model
    Access the printer's web UI (embedded web server) or print a configuration page to confirm the exact model number. Check if the model is one of: Canon Mf755cdw, Mf753cdw, Mf751cdw, Lbp674c, Lbp672c, Lbp671c, Mf1238 Ii, or Mf1333c.
    Affected if The device model matches one of the affected models listed in the CVE.
  2. Check installed firmware version
    In the printer's web UI, navigate to the Device Information or Settings section to view the firmware version. Alternatively, print a configuration page from the device control panel.
    Affected if The firmware version is 03.07 or lower (any version <= 03.07).
  3. Verify SLP protocol status
    In the printer's web UI, locate the network settings or protocol configuration section. Look for SLP (Service Location Protocol) settings and confirm whether it is enabled or disabled.
    Affected if SLP is enabled on the device - this is the attack surface for the buffer overflow.
  4. Confirm network exposure
    Review network configuration to determine if the printer is accessible from network segments where untrusted users or devices may reside.
    Affected if The printer is on a network segment accessible to untrusted users, combined with SLP being enabled.

You are affected if your device is one of the listed Canon models AND runs firmware version 03.07 or lower AND has SLP protocol enabled and is network-accessible.

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

Isolate affected printers in a dedicated network segment with restricted access, and apply firmware version v03.08 or later when released by Canon to address this vulnerability.

Recommended fix Moderate confidence

Firmware version > 03.07 (check Canon support site for exact latest version for your model)

  1. 1. Identify the exact Canon printer model from the affected list (Mf755cdw, Mf753cdw, Mf751cdw, Lbp674c, Lbp672c, Lbp671c, Mf1238 Ii, or Mf1333c)
  2. 2. Access the Canon support website for your region (canon.jp, www.usa.canon.com, or www.canon-europe.com depending on location of purchase)
  3. 3. Navigate to the support/drivers section for your specific printer model
  4. 4. Locate and download the latest firmware version available - look for versions numbered higher than 03.07
  5. 5. Consult the printer's user manual for firmware update instructions (typically involves connecting via USB or network and using Canon's firmware update utility)
  6. 6. Apply the firmware update following the vendor's documented procedure
  7. 7. After update, verify the firmware version has changed from <=03.07 to the newer version
  8. 8. Consider network segmentation to limit exposure until the patch is applied
Caveat Firmware updates typically require downtime and may reset some device settings; backup configuration if possible before updating

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

Fix this in Mf755cdw Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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