CVE-2024-12649
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 · uneditedBuffer overflow in XPS data font processing of 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 MF656Cdw/Satera MF654Cdw firmware v05.04 and earlier sold in Japan. Color imageCLASS MF656Cdw/Color imageCLASS MF654Cdw/Color imageCLASS MF653Cdw/Color imageCLASS MF652Cdw/Color imageCLASS LBP633Cdw/Color imageCLASS LBP632Cdw firmware v05.04 and earlier sold in US. i-SENSYS MF657Cdw/i-SENSYS MF655Cdw/i-SENSYS MF651Cdw/i-SENSYS LBP633Cdw/i-SENSYS LBP631Cdw firmware v05.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 confidenceA buffer overflow vulnerability exists in the XPS data font processing component of multiple Canon Satera, Color imageCLASS, and i-SENSYS printer models running firmware v05.04 and earlier. By sending specially crafted XPS data containing malicious font information, an attacker on the same network segment can potentially cause the device to become unresponsive or achieve arbitrary code execution with elevated privileges.
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<= 05.04<= 05.04<= 05.04<= 05.04<= 05.04<= 05.04<= 05.04<= 05.04CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify printer modelCheck the product label on the device or access the web interface (http://<printer-ip>) to view the model name under Device Information or StatusAffected if Model is one of: Mf455dw, Mf453dw, Mf452dw, Mf451dw, Mf465dw, Mf462dw, Mf656cdw, or Mf654cdw
-
Check installed firmware versionAccess the printer web interface, navigate to Settings or Device Information page to view the firmware version; alternatively, print a configuration page from the control panelAffected if Firmware version displayed is 05.04 or earlier (e.g., 05.04, 05.03, 05.02, etc.)
-
Confirm network accessibilityPing the printer IP address or check if port 80/443 (web UI) or port 9100 (raw print) is responding from your workstationAffected if Printer is reachable from network segments that contain untrusted users or systems
-
Verify XPS print job processing is enabledCheck printer settings via web UI under Security or Port settings to confirm XPS/RAW printing ports are open; note that XPS processing is typically enabled by default for standard print workflowsAffected if Printer accepts print jobs via XPS format or RAW port 9100 from network clients
Device is affected if it matches one of the listed models AND has firmware version 05.04 or earlier AND is accessible on a network where an attacker could send malicious XPS data.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply the vendor-provided firmware update (v05.05 or later) when released. Until then, isolate affected devices on a restricted network segment to reduce attack surface.
Firmware version newer than 05.04 (check Canon support sites for exact latest version per model)
- 1. Identify the exact Canon printer model from the affected list (MF455dw, MF453dw, MF452dw, MF451dw, MF465dw, MF462dw, MF656cdw, MF654cdw or regional variants)
- 2. Visit the official Canon support website for your region (canon.jp, canon-europe.com, or usa.canon.com)
- 3. Navigate to the product support/ drivers and downloads section for your specific printer model
- 4. Locate the firmware update section and check for versions newer than 05.04
- 5. Download the latest firmware version available from Canon's official site
- 6. Follow Canon's provided firmware update instructions (typically involves connecting the printer via USB or network and running the firmware update utility)
- 7. After updating, verify the firmware version has changed from 05.04 or earlier to the newer version
- 8. Confirm the printer is functioning normally after the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-12649 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-12649 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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