CVE-2023-0853
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 mDNS NSEC record registering process 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 confidenceA buffer overflow vulnerability exists in the mDNS NSEC (Next Secure) record registration process of affected Canon printer firmware versions 11.04 and earlier. An attacker on the same network segment can send specially crafted mDNS packets that overflow a buffer during NSEC record handling, potentially causing the device to become unresponsive (Denial of Service) or allowing 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<= 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 printer modelCheck the printer model label on the device or via the printer's web interface (usually accessed via IP address)Affected if Model is one of: Mf642cdw, Mf644cdw, Mf741cdw, Mf743cdw, Mf745cdw, Lbp621c, Lbp622c, Lbp661c
-
Check firmware versionAccess the printer's web interface and navigate to the firmware or device information page, or print a configuration page from the printer control panelAffected if Firmware version is 11.04 or earlier
-
Verify mDNS service statusCheck the printer's network settings via the web interface for mDNS/Bonjour service configuration, or use network scanning tools to detect if port 5353 (mDNS) is open on the printer IPAffected if mDNS is enabled and the printer is reachable on the network
A user is affected if they have one of the listed Canon printer models running firmware version 11.04 or earlier with mDNS service enabled on their network.
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 Canon firmware version 11.05 or later for all affected printer models. Until patched, network isolation and segmentation should be implemented to limit exposure to untrusted network segments.
Firmware version > 11.04 (latest available firmware from Canon for your specific model)
- Identify the specific Canon printer model from the affected list (MF642cdw, MF644cdw, MF741cdw, MF743cdw, MF745cdw, LBP621c, LBP622c, LBP661c)
- Navigate to the official Canon support website for your region (canon.jp, canon-europe.com, or usa.canon.com depending on sales region)
- Locate the drivers and firmware section for your specific printer model
- Download the latest firmware version available (versions greater than 11.04 contain the security fix)
- Access the printer's web interface or use Canon firmware update utility
- Upload and apply the firmware update following Canon's documented procedure
- Verify the firmware version after update confirms successful installation
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-2023-0853 — 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-0853 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