CVE-2019-14309
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 · uneditedRicoh SP C250DN 1.05 devices have a fixed password. FTP service credential were found to be hardcoded within the printer firmware. This would allow to an attacker to access and read information stored on the shared FTP folders.
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 confidenceRicoh SP C250DN printer firmware version 1.05 contains hardcoded FTP service credentials embedded in the firmware image. An unauthenticated remote attacker can use these fixed credentials to access the device's FTP service and read information stored in shared FTP folders, leading to information disclosure.
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 dataall versionsall versions= 1.05all versionsCVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 modelCheck the device label or access the printer's web interface or control panel to confirm the exact model number (SP C250DN, SP C250sf, SP C252sf, or SP C252dn)Affected if The device is any of these four models
-
Check the installed firmware versionAccess the printer's web interface (typically via HTTP to the device IP), navigate to the firmware or system information page, and note the firmware version displayedAffected if For SP C250DN the version is 1.05; for SP C250sf, SP C252sf, or SP C252dn any firmware version is affected
-
Verify if FTP service is enabledAccess the printer's web interface and check the network services or FTP settings section to see if the FTP server/ service is turned onAffected if FTP service is enabled on the device
-
Confirm FTP folder access configurationIn the FTP settings, check if any shared folders or FTP directories are configured for read accessAffected if FTP folders are shared and accessible
-
Review network exposure of the FTP portScan the device IP for open port 21 (FTP) from the network or check the firewall/access control settings to determine if the FTP service is reachable from untrusted networksAffected if Port 21 is accessible from untrusted network segments
The environment is affected if the device is one of the four listed Ricoh models, runs the indicated firmware version, and has FTP service enabled and 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.
From vendor dataContact Ricoh for available firmware updates to replace hardcoded credentials; if no update exists, disable the FTP service or isolate the device on a restricted network segment to limit exposure.
- Consultation3.0 h
- Implementation4.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,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14309 — 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-14309 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