dbcve.org
Mg3100 PrinterHardware / appliance · Canon

CVE-2013-4615

MEDIUM · 5.0 CVSS v2.0 Published 2013-06-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
The Canon MG3100, MG5300, MG6100, MP495, MX340, MX870, MX890, MX920, and MX922 printers allow remote attackers to cause a denial of service (device hang) via a crafted LAN_TXT24 parameter to English/pages_MacUS/cgi_lan.cgi followed by a direct request to English/pages_MacUS/lan_set_content.html. NOTE: the vendor has apparently responded by stating "Canon believes that its printers will not have to deal with unauthorized access to the network from an external location as long as the printers are used in a secured environment."

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 · moderate confidence

This is a denial of service vulnerability in Canon printer firmware affecting multiple models (MG3100, MG5300, MG6100, MP495, MX340, MX870, MX890, MX920, MX922). Attackers can cause device hang by sending a crafted LAN_TXT24 parameter to the cgi_lan.cgi endpoint followed by a request to lan_set_content.html, both under English/pages_MacUS/. The attack exploits the web interface of the printer.

MitigationSince Canon has not released a firmware patch and considers this a network boundary issue, organizations should isolate affected printers on a dedicated VLAN, implement firewall rules restricting access to the printer's web interface to trusted internal IPs only, and consider replacing affected devices with newer models that receive security updates.

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
Mg3100 PrinterHardware / appliance
Affected:all versions
Mg5300 PrinterHardware / appliance
Affected:all versions
Mg6100 PrinterHardware / appliance
Affected:all versions
Mp340 PrinterHardware / appliance
Affected:all versions
Mp495 PrinterHardware / appliance
Affected:all versions
Mx870 PrinterHardware / appliance
Affected:all versions
Mx890 PrinterHardware / appliance
Affected:all versions
Mx920 PrinterHardware / appliance
Affected:all versions

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
Authentication
None
Confidentiality
None
Integrity
None
Availability
Partial

AV:N/AC:L/Au:N/C:N/I:N/A:P

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 model on the network
    Access the printer's web interface via its IP address and locate the model number in the header, footer, or system settings page. Alternatively, check DHCP lease tables, network scans, or printer documentation.
    Affected if The printer model is one of: MG3100, MG5300, MG6100, MP340, MP495, MX870, MX890, MX920, or MX922.
  2. Verify the printer web interface is accessible
    Attempt to access http://<printer-ip>/ (or the English/pages_MacUS/ path) from a browser or via curl. Check for HTTP response.
    Affected if The web interface returns an HTTP 200 response, indicating it is online and reachable.
  3. Confirm the cgi_lan.cgi endpoint exists
    Navigate to English/pages_MacUS/cgi_lan.cgi or send a GET request to http://<printer-ip>/English/pages_MacUS/cgi_lan.cgi
    Affected if The endpoint returns a valid response or error message from the printer's CGI interface.
  4. Check if lan_set_content.html is accessible
    Navigate to English/pages_MacUS/lan_set_content.html or send a GET request to this path
    Affected if The page loads or returns a response from the printer's web server.

If the printer model matches any of the affected models (MG3100, MG5300, MG6100, MP340, MP495, MX870, MX890, MX920, MX922) AND the web interface at English/pages_MacUS/ is accessible on the network, the environment is affected by this CVE.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since Canon has not released a firmware patch and considers this a network boundary issue, organizations should isolate affected printers on a dedicated VLAN, implement firewall rules restricting access to the printer's web interface to trusted internal IPs only, and consider replacing affected devices with newer models that receive security updates.

Fix this in Mg3100 Printer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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 locally
dbcve dependency scanner

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