CVE-2025-14236
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 Address Book attribute tag processing on Small Office Multifunction 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 v06.02 and earlier sold in Japan.Color imageCLASS LBP630C/Color imageCLASS MF650C Series/imageCLASS LBP230 Series/imageCLASS X LBP1238 II/imageCLASS MF450 Series/imageCLASS X MF1238 II/imageCLASS X MF1643i II/imageCLASS X MF1643iF II firmware v06.02 and earlier sold in US.i-SENSYS LBP630C Series/i-SENSYS MF650C Series/i-SENSYS LBP230 Series/1238P II/1238Pr II/i-SENSYS MF450 Series/i-SENSYS MF550 Series/1238i II/1238iF II/imageRUNNER 1643i II/imageRUNNER 1643iF II firmware v06.02 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 Address Book attribute tag processing of multiple Canon small office multifunction printer firmware versions v06.02 and earlier. An attacker on the same network segment can send specially crafted packets to trigger the overflow, potentially causing the device to become unresponsive (denial of service) or achieving arbitrary code execution with elevated privileges on the affected printer.
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<= 06.02<= 06.02<= 06.02<= 06.02<= 06.02<= 06.02<= 06.02<= 06.02CVSS 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 modelAccess the printer's web interface or control panel to confirm the exact model number (MF455dw, MF453dw, MF452dw, MF451dw, MF654cdw, MF656cdw, MF653cdw, or MF652cw)Affected if The model matches one of the eight affected Canon models listed in the advisory
-
Check installed firmware versionIn the printer's web interface, navigate to Device Information or System Settings and locate the firmware version field. Compare the displayed version against the affected range.Affected if Firmware version is 06.02 or an earlier version number
-
Verify Address Book feature statusIn the printer's web interface, locate the Address Book or LDAP/Network Address Book settings section. Confirm whether this feature is enabled or configured.Affected if Address Book functionality is enabled or configured on the device
-
Confirm network accessibilityDetermine if the printer is reachable from network segments outside of a dedicated, isolated VLAN. Verify the printer's IP address and subnet placement.Affected if Printer is accessible from network segments containing untrusted or unknown devices
Device is affected if it is one of the eight listed Canon models running firmware version 06.02 or earlier, with Address Book feature enabled, and reachable by network-adjacent attackers.
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 to version v06.03 or later. If patching is not immediately possible, restrict network access to trusted hosts and disable unnecessary network services on affected devices.
Firmware version newer than 06.02 (exact version number available from Canon's official support channels)
- Check Canon support sites (canon.jp, psirt.canon, www.canon-europe.com, www.usa.canon.com) for firmware updates addressing CVE-2025-14236
- Download the latest firmware version for your specific printer model from Canon's official support portal
- Follow Canon's firmware update instructions specific to your model (typically involves uploading firmware via web interface or USB connection
- Verify the firmware version has been updated to a version newer than 06.02 after the update process
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-14236 — 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-2025-14236 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