CVE-2019-14308
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 · uneditedSeveral Ricoh printers have multiple buffer overflows parsing LPD packets, which allow an attacker to cause a denial of service or code execution via crafted requests to the LPD service. Affected firmware versions depend on the printer models. One affected configuration is cpe:2.3:o:ricoh:sp_c250dn_firmware:-:*:*:*:*:*:*:* up to (including) 1.06 running on cpe:2.3:o:ricoh:sp_c250dn:-:*:*:*:*:*:*:*, cpe:2.3:o:ricoh:sp_c252dn:-:*:*:*:*:*:*:*. Another affected configuration is cpe:2.3:o:ricoh:sp_c250sf_firmware:-:*:*:*:*:*:*:* up to (including) 1.12 running on cpe:2.3:o:ricoh:sp_c250sf:-:*:*:*:*:*:*:*, cpe:2.3:o:ricoh:sp_c252sf:-:*:*:*:*:*:*:*.
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 confidenceMultiple buffer overflow vulnerabilities exist in the LPD (Line Printer Daemon) service of specific Ricoh printer models (SP C250dn, SP C252dn, SP C250sf, SP C252sf) when parsing incoming LPD packets. These flaws allow remote attackers to cause denial of service or achieve arbitrary code execution with crafted malicious LPD requests.
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< 1.13< 1.13< 1.07< 1.07CVSS 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.0/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 Ricoh printer modelAccess the printer's web interface or print a configuration page to confirm the exact model number (SP C250dn, SP C252dn, SP C250sf, or SP C252sf)Affected if The model is not one of the four affected models listed in the CVE
-
Check the firmware versionVia the printer's web interface under 'Device Settings' or 'System Settings', or print a configuration/status page to view the current firmware versionAffected if The installed firmware version is below 1.13 for SP C250sf/SP C252sf, or below 1.07 for SP C250dn/SP C252dn
-
Determine if LPD service is enabledAccess the printer's web interface and navigate to Network Settings or Services to verify if the LPD (Line Printer Daemon) service is turned on; alternatively, attempt a connection to port 515/tcpAffected if The LPD service is enabled and port 515/tcp is accessible
-
Verify LPD is exposed to untrusted networksScan the network to confirm port 515/tcp is open and assess whether the printer is accessible from network segments that contain untrusted or external systemsAffected if Port 515/tcp is open and the printer is reachable from networks beyond the trusted local segment
You are affected if you have a Ricoh SP C250sf, SP C252sf with firmware below 1.13, or SP C250dn/SP C252dn with firmware below 1.07, AND the LPD service is enabled and accessible.
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 · scoped1.071.13
Update printer firmware to the latest patched version released by Ricoh; alternatively, disable the LPD service if not required and block LPD ports (515/tcp) at network boundaries.
Sp C250sf/C252sf: Firmware 1.13 or later; Sp C250dn/C252dn: Firmware 1.07 or later
- Identify the exact model number (Sp C250sf, Sp C252sf, Sp C250dn, or Sp C252dn) of the Ricoh printer
- Access the printer's web management interface or control panel
- Navigate to the firmware update section (usually under Settings, Maintenance, or Device Settings)
- Download the firmware update from Ricoh's official support website (ricoh.com or ricoh-usa.com) matching your exact model and current version
- Upload and install the firmware version 1.13 or later for Sp C250sf/Sp C252sf models
- Upload and install the firmware version 1.07 or later for Sp C250dn/Sp C252dn models
- After firmware update, verify the LPD service is running and the version has changed
- Consider disabling the LPD service if not required, as an additional hardening step
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-2019-14308 — 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-2019-14308 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