dbcve.org
I Sensys Mf754cdw FirmwareOperating system · Canon

CVE-2024-0244

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 CPCA PCFAX number 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 MF750C Series firmware v03.07 and earlier sold in Japan. Color imageCLASS MF750C Series/Color imageCLASS X MF1333C firmware v03.07 and earlier sold in US. i-SENSYS MF754Cdw/C1333iF 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 · high confidence

Buffer overflow vulnerability in the CPCA PCFAX number processing component of Canon multifunction printers (Satera MF750C, Color imageCLASS MF750C/X MF1333C, i-SENSYS MF754Cdw/C1333iF). An attacker on the same network segment can trigger the overflow to cause device unresponsiveness or achieve arbitrary code execution.

MitigationUpdate affected device firmware to v03.07 or later as provided by Canon. Network segmentation and access controls should be implemented to limit exposure to only trusted network segments.

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
I Sensys Mf754cdw FirmwareOperating system
Affected:<= 03.07
I Sensys X C1333if FirmwareOperating system
Affected:<= 03.07
Mf755cdw FirmwareOperating system
Affected:<= 03.07
Mf753cdw FirmwareOperating system
Affected:<= 03.07
Mf751cdw FirmwareOperating system
Affected:<= 03.07
Mf1333c FirmwareOperating system
Affected:<= 03.07
Lbp1333c 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 Canon printer models on the network
    Scan the network for Canon multifunction printer devices or manually locate model numbers on the device physical labels or web interface. Look for: I-Sensys MF754cdw, I-Sensys X C1333if, MF755cdw, MF753cdw, MF751cdw, MF1333c, LBP1333c, Satera MF750C, or Color imageCLASS MF750C/X MF1333C.
    Affected if Any of the listed Canon printer models are present on the network.
  2. Check the installed firmware version
    Access the printer web administration panel (typically http://<printer-ip>/) and navigate to the Firmware or Device Information section to view the current firmware version. Alternatively, check via the printer control panel under Device Settings or System Information.
    Affected if The firmware version is <= 03.07 for any of the affected models listed.
  3. Verify PCFAX functionality is accessible
    Check if the PCFAX or Fax feature is enabled in the printer web interface under Fax or Communication settings. Confirm the CPCA (Canon Printer Control Application) service is running or accessible on the device.
    Affected if PCFAX functionality is enabled and the CPCA service is accessible on the device.
  4. Assess network accessibility of the PCFAX service
    Determine if the printer is on a network segment accessible to untrusted users. Check if the printer management interface and fax services are exposed to network segments outside of the trusted internal network.
    Affected if The printer and its PCFAX service are accessible from network segments that include untrusted or unknown users.

You are affected if you have any Canon I-Sensys MF754cdw, MF755cdw, MF753cdw, MF751cdw, MF1333c, LBP1333c, or Color imageCLASS/Satera MF750C/X MF1333C devices running firmware version 03.07 or lower, with PCFAX enabled and accessible from your 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 03.07
Interim mitigation

Update affected device firmware to v03.07 or later as provided by Canon. Network segmentation and access controls should be implemented to limit exposure to only trusted network segments.

Recommended fix Moderate confidence

Firmware v03.08 or later (consult Canon support for exact fixed version for your specific model)

  1. 1. Identify the exact Canon printer model number and current firmware version from the device's control panel or web interface
  2. 2. Navigate to the official Canon support page for your specific printer model (canon.com, canon-europe.com, or canon.jp depending on region)
  3. 3. Locate the firmware download section and check for newer firmware versions
  4. 4. Download the latest firmware update file provided by Canon
  5. 5. Follow Canon's firmware update instructions, which typically involve: accessing the device's web interface, navigating to the maintenance or firmware update section, and uploading the downloaded firmware file
  6. 6. After update completion, verify the new firmware version displays the corrected version (v03.08 or later)
  7. 7. Restart the device to ensure the firmware update is fully applied
Caveat Firmware updates on Canon devices typically do not introduce breaking changes but should be performed while the device is powered on and connected to a stable power source to avoid rendering the device inoperable

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

Fix this in I Sensys Mf754cdw Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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