dbcve.org
Sp C250sf FirmwareOperating system · Ricoh

CVE-2019-14300

CRITICAL · 9.8 CVSS v3.0 Published 2019-08-26
Fix available
A fix is available. Upgrade to 1.07 / 1.13 or later.
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
Several Ricoh printers have multiple buffer overflows parsing HTTP cookie headers, 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 confidence

Multiple buffer overflow vulnerabilities exist in the web server component of several Ricoh printer models (SP C250DN, SP C252DN, SP C250SF, SP C252SF) when parsing HTTP cookie headers. Crafted requests containing oversized or malformed cookie data can trigger heap or stack-based overflows, enabling denial of service or potentially remote code execution with the privileges of the web server process.

MitigationUpdate printer firmware to versions beyond 1.06 (for C250DN/C252DN) and 1.12 (for C250SF/C252SF). Additionally, restrict network access to the printer web interface using firewall rules or network segmentation to limit exposure to untrusted attackers.

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
Sp C250sf FirmwareOperating system
Affected:< 1.13
Sp C252sf FirmwareOperating system
Affected:< 1.13
Sp C250dn FirmwareOperating system
Affected:< 1.07
Sp C252dn FirmwareOperating system
Affected:< 1.07

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

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

  1. Identify the printer model
    Access the printer's web interface or control panel to confirm the exact model number (SP C250DN, SP C252DN, SP C250SF, or SP C252SF). If unknown, check the device label or printed test page.
    Affected if The model is not one of the four affected models listed in the CVE.
  2. Determine the installed firmware version
    Log in to the printer web interface and navigate to the Device Information or Firmware version page. Alternatively, print a configuration page from the control panel to view the firmware version.
    Affected if The firmware version is below 1.07 for C250DN/C252DN models, or below 1.13 for C250SF/C252SF models.
  3. Verify the web server component is enabled
    Confirm that the embedded web server (Web Image Monitor or similar) is accessible by attempting to reach the printer IP address on HTTP/HTTPS ports (typically 80 or 443). Check printer network settings to ensure the web service is turned on.
    Affected if The web server component is disabled or inaccessible, as the vulnerability exists within this component when parsing HTTP cookie headers.
  4. Assess network exposure of the web interface
    Review network configuration, firewall rules, or VLAN assignment to determine if the printer web interface is reachable from untrusted network segments or the internet.
    Affected if The web interface is exposed to untrusted users or networks, increasing the likelihood of exploitation attempts.

You are affected if you own an SP C250DN, SP C252DN, SP C250SF, or SP C252SF printer with firmware below 1.07 (DN models) or 1.13 (SF models) and the web server component is enabled and network-accessible.

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.

dbcve · scoped
Upgrade available Upgrade to 1.07 / 1.13 or later
Fixed in 1.071.13
Interim mitigation

Update printer firmware to versions beyond 1.06 (for C250DN/C252DN) and 1.12 (for C250SF/C252SF). Additionally, restrict network access to the printer web interface using firewall rules or network segmentation to limit exposure to untrusted attackers.

Recommended fix High confidence

Sp C250sf/Sp C252sf: firmware 1.13 | Sp C250dn/Sp C252dn: firmware 1.07

  1. Identify the exact Ricoh printer model (Sp C250sf, Sp C252sf, Sp C250dn, or Sp C252dn)
  2. Access the printer's web management interface or control panel to check the current firmware version
  3. Download the latest firmware from Ricoh's official support website (www.ricoh.com or www.ricoh-usa.com)
  4. Follow Ricoh's standard firmware update procedure - typically via the web interface under 'Administrator' > 'Firmware Update' or using Ricoh's firmware update utility
  5. After updating, verify the firmware version has been changed to the fixed release: 1.13 or higher for Sp C250sf/Sp C252sf, or 1.07 or higher for Sp C250dn/Sp C252dn
Caveat Firmware updates typically require temporary downtime; ensure print jobs are paused and configuration is backed up before proceeding

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sp C250sf Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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