Sp C250sf FirmwareOperating system · Ricoh

CVE-2019-14305

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

NVD · unedited

Several Ricoh printers have multiple buffer overflows parsing HTTP parameter settings for Wi-Fi, mDNS, POP3, SMTP, and notification alerts, 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

dbcve analysis · high confidence

Multiple buffer overflow vulnerabilities exist in Ricoh printer web servers when parsing HTTP parameter settings for Wi-Fi, mDNS, POP3, SMTP, and notification alerts. Attackers can send crafted HTTP requests with oversized parameters to trigger heap/stack overflows, potentially achieving arbitrary code execution or causing denial of service.

MitigationUpdate affected printer firmware to patched versions beyond 1.06 (SP C250dn/C252dn) and 1.12 (SP C250sf/C252sf). If patching is not immediately possible, disable or restrict access to the web management interface and place printers in isolated network segments.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

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

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?

dbcve checks

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

Identify the printer model

Check the device label or access the web interface to confirm the exact model number (SP C250sf, SP C252sf, SP C250dn, or SP C252dn)

Affected if The model is not one of the four affected models listed
Check the installed firmware version

Access the printer web management interface and navigate to the status or device information page to view the firmware version; alternatively, print a configuration page from the control panel

Affected if The firmware version is below 1.07 for SP C250dn/C252dn, or below 1.13 for SP C250sf/C252sf
Verify the web management interface is accessible

Attempt to access the printer's web interface by entering the printer IP address in a web browser; confirm the HTTP service is responding

Affected if The web interface is exposed and reachable on the network
Confirm HTTP parameter handling features are in use

Check if Wi-Fi, mDNS, POP3, SMTP, or notification alert settings are configurable through the web interface; these are the features with vulnerable parameter parsing

Affected if Any of these features are enabled and accessible via the web interface

You are affected if you have an SP C250sf, SP C252sf, SP C250dn, or SP C252dn printer with firmware below the patched version AND the web management interface is accessible and handling the vulnerable features.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 1.07 / 1.13 or later

Fixed in 1.071.13

Interim mitigation

Update affected printer firmware to patched versions beyond 1.06 (SP C250dn/C252dn) and 1.12 (SP C250sf/C252sf). If patching is not immediately possible, disable or restrict access to the web management interface and place printers in isolated network segments.

Recommended fix High confidence

Sp C250sf/C252sf: firmware >= 1.13; Sp C250dn/C252dn: firmware >= 1.07

Identify the exact printer model (Sp C250sf, Sp C252sf, Sp C250dn, or Sp C252dn) and current firmware version via the printer's control panel or web interface
Navigate to the official Ricoh support website (www.ricoh.com or www.ricoh-usa.com) and locate the firmware download section for the specific printer model
Download the firmware update file corresponding to the printer model: Sp C250sf/C252sf requires version 1.13 or later; Sp C250dn/C252dn requires version 1.07 or later
Access the printer's web administration interface and navigate to the firmware update or system maintenance section
Upload and apply the downloaded firmware update file, following the on-screen instructions
After the firmware update completes, verify the new firmware version matches or exceeds the required fixed version (1.13 for C250sf/C252sf, 1.07 for C250dn/C252dn)
Restart the printer and confirm all network services (HTTP, Wi-Fi, mDNS, POP3, SMTP) are functioning normally

Caveat Firmware updates may temporarily interrupt print jobs; ensure no critical print jobs are running before initiating the update

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
Implementation6.0 h
Testing3.0 h
Review / QA2.0 h

14.0 hours of engineering $2,490

Get the upgrade done

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-14305 — 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

Primary sources

www.ricoh.comVendor Advisory
www.ricoh-usa.comProduct
jvn.jp
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-14305 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2019-14305?

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.

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

At a glance

A fix existsUpgrade to 1.07 / 1.13 or later

Severity 9.8 Critical

Exploit likelihood EPSS, next 30 days 3.0%

Affects: Sp C250sf Firmware

Remediation

A high-priority fix

Fix this in Sp C250sf Firmware 14 hrs · Moderate

Typical engagement from $2,490

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2019-14305 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References