Ecosys M5526cdw FirmwareOperating system · Kyocera

CVE-2019-13201

CRITICAL · 9.8 CVSS v3.1 Published 2020-03-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Some Kyocera printers (such as the ECOSYS M5526cdw 2R7_2000.001.701) were affected by a buffer overflow vulnerability in the LPD service. This would allow an unauthenticated attacker to cause a Denial of Service (DoS) in the LPD service and potentially execute arbitrary code on the device.

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

A buffer overflow vulnerability exists in the LPD (Line Printer Daemon) service of certain Kyocera printers (ECOSYS M5526cdw 2R7_2000.001.701 and potentially similar models). An unauthenticated remote attacker can send specially crafted requests to port 515/tcp, causing a denial of service in the LPD service and potentially achieving arbitrary code execution with elevated privileges on the affected device.

MitigationDisable the LPD service on affected Kyocera printers if not required for business operations, or apply vendor firmware updates when available. Restrict network access to port 515/tcp via firewall rules to limit exposure to trusted hosts only.

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
Ecosys M5526cdw FirmwareOperating system
Affected:= 2r7_2000.001.701

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the printer model
    Access the printer's web administration interface or print a configuration page to confirm the exact model number (look for Kyocera Ecosys M5526cdw or similar Kyocera models)
    Affected if The device is a Kyocera Ecosys M5526cdw printer
  2. Check the firmware version
    In the printer's web interface, navigate to the Device Information or Firmware section, or print a status/configuration page to display the current firmware version
    Affected if The firmware version is 2r7_2000.001.701 exactly, or falls within the affected version range if additional versions are later identified
  3. Verify LPD service is enabled
    In the printer web interface, check the LPD/LPR settings under Network Configuration or Protocol settings. Alternatively, scan port 515/tcp using a network scanner (nmap -p 515 <printer-ip>) to confirm the port is listening
    Affected if Port 515/tcp is open and the LPD service is enabled on the device
  4. Check network exposure to LPD port
    Review firewall rules or network segmentation to determine if port 515/tcp is accessible from untrusted networks or the internet. Use external port scanning tools to verify if the port is exposed
    Affected if Port 515/tcp is accessible from untrusted network segments or directly from the internet

You are affected if you have a Kyocera Ecosys M5526cdw device running firmware version 2r7_2000.001.701 with the LPD service enabled and accessible to potential attackers.

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

Disable the LPD service on affected Kyocera printers if not required for business operations, or apply vendor firmware updates when available. Restrict network access to port 515/tcp via firewall rules to limit exposure to trusted hosts only.

Fix this in Ecosys M5526cdw Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-13201 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-13201 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