CVE-2019-14307
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 HTTP parameter settings for SNMP, which allow an attacker to cause a denial of service or code execution via crafted requests to the web server. 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 in Ricoh printer web servers allow remote attackers to cause denial of service or achieve code execution by sending crafted HTTP requests with malicious SNMP parameter settings. The vulnerabilities affect SP C250dn, SP C252dn, SP C250sf, and SP C252sf models running firmware versions up to 1.06 and 1.12 respectively.
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 web interface (HTTP/HTTPS) or check the device label/menu to confirm the exact model number is one of: SP C250dn, SP C252dn, SP C250sf, or SP C252sfAffected if The model is any of these four affected models
-
Check the firmware versionLog into the printer web interface and navigate to the System or Settings page to view the firmware version, or print a configuration page from the device menuAffected if Firmware version is below 1.13 for SP C250sf/SP C252sf, or below 1.07 for SP C250dn/SP C252dn
-
Verify the web server is accessibleAttempt to reach the printer IP address on HTTP (port 80) or HTTPS (port 443) from the networkAffected if The web interface is reachable over the network
-
Confirm SNMP management is availableAccess the web interface and check the SNMP or Network settings section to see if SNMP configuration options are present and enabledAffected if SNMP is enabled and configurable through the web interface
A user is affected if they have one of the four listed Ricoh printer models running firmware below the threshold (1.13 for sf models, 1.07 for dn models) with the web server and SNMP accessible on the 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 · scoped1.071.13
Apply vendor-released firmware updates to patch the buffer overflow vulnerabilities. If patches are unavailable, consider network segmentation to limit web server exposure and disable SNMP management interfaces if not required.
Firmware 1.13 (for Sp C250sf/Sp C252sf) or Firmware 1.07 (for Sp C250dn/Sp C252dn)
- Identify the specific Ricoh printer model (Sp C250sf, Sp C252sf, Sp C250dn, or Sp C252dn) from the affected product list
- Download the appropriate firmware update from Ricoh's official support website (www.ricoh.com or www.ricoh-usa.com)
- For Sp C250sf and Sp C252sf models: Upgrade firmware to version 1.13 or later
- For Sp C250dn and Sp C252dn models: Upgrade firmware to version 1.07 or later
- Follow Ricoh's standard firmware update procedure, which typically involves uploading the firmware file through the printer's web administration interface or using Ricoh's firmware update utility
- After updating, verify the firmware version has been successfully applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14307 — 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-14307 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