CVE-2023-0852
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 the Address Book of Mobile Device function of Office / 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 LBP660C Series/LBP620C Series/MF740C Series/MF640C Series firmware Ver.11.04 and earlier sold in Japan. Color imageCLASS LBP660C Series/LBP 620C Series/X LBP1127C/MF740C Series/MF640C Series/X MF1127C firmware Ver.11.04 and earlier sold in US. i-SENSYS LBP660C Series/LBP620C Series/MF740C Series/MF640C Series, C1127P, C1127iF, C1127i firmware Ver.11.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 confidenceBuffer overflow vulnerability in the Address Book of Mobile Device function of Canon Satera, Color imageCLASS, and i-SENSYS multifunction printers and laser printers running firmware Ver.11.04 and earlier allows a network-adjacent attacker to cause device unresponsiveness or potentially execute arbitrary code due to improper bounds checking in the address book handling for mobile device connections.
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<= 11.04<= 11.04<= 11.04<= 11.04<= 11.04<= 11.04<= 11.04<= 11.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 the Canon printer modelCheck the product label on the device or access the web interface (Remote UI) at the printer's IP address to confirm the exact model number matches one of the affected models: Mf642cdw, Mf644cdw, Mf741cdw, Mf743cdw, Mf745cdw, Lbp621c, Lbp622c, or Lbp661cAffected if The model is any of the eight listed affected product names
-
Check the installed firmware versionAccess the printer web interface (Remote UI) and navigate to Settings/Registration > Device Information, or print a system settings report from the control panel to view the current firmware versionAffected if The firmware version displayed is 11.04 or lower (for example, 11.03, 11.02, 10.x, etc.)
-
Verify Mobile Device connectivity is enabledAccess the web interface and check Settings/Registration > Network > Mobile Device Connection Settings, or check the control panel under Network settings to see if Wi-Fi Direct, AirPrint, or other mobile device connection features are enabledAffected if Mobile device connectivity features (Wi-Fi Direct, AirPrint, Canon PRINT Business) are turned on, making the Address Book of Mobile Device function accessible
-
Confirm Address Book feature accessCheck if the Address Book function is accessible via the Remote UI under Address Book settings, or verify that mobile device synchronization or contact import features are configuredAffected if The Address Book function is available or configured for mobile device connections, which is the vulnerable component
The environment is affected if the printer model matches one of the eight listed products, the firmware version is 11.04 or earlier, and Mobile Device connectivity with Address Book access is enabled, allowing a network-adjacent attacker to trigger the buffer overflow.
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.
From vendor dataUpdate Canon printer firmware to version 11.05 or later for all affected device series (Satera, Color imageCLASS, i-SENSYS) to remediate the buffer overflow in the Address Book of Mobile Device function.
- 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-2023-0852 — 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-2023-0852 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