# CVE-2019-14304: Ricoh SP C250DN 1.06 devices allow CSRF.


- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Jan 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-34qx-g8h3-chw9

## What is CVE-2019-14304?

CVE-2019-14304 is a high-severity vulnerability in n/a, published on 10 Jan 2020. 

### Official description

Ricoh SP C250DN 1.06 devices allow CSRF.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2019-14304?

It affects 52 products.


Products: Ricoh M 2700 Firmware, Ricoh M 2701 Firmware, Ricoh M C250fw Firmware, Ricoh M C250fwb Firmware, Ricoh Mp 2014 Firmware, Ricoh Mp 2014ad Firmware, Ricoh Mp 2014d Firmware, Ricoh P C300w Firmware, Ricoh P C301w Firmware, Ricoh Sp277nwx Firmware, Ricoh Sp 212nw Firmware, Ricoh Sp 212sfnw \(China\) Firmware, Ricoh Sp 212sfnw Firmware, Ricoh Sp 212sfw Firmware, Ricoh Sp 212snw Firmware, Ricoh Sp 212suw Firmware, Ricoh Sp 212w Firmware, Ricoh Sp 213nw \(Taiwan\) Firmware, Ricoh Sp 213nw Firmware, Ricoh Sp 213sfnw \(Taiwan\) Firmware and 32 more.

## How do I fix CVE-2019-14304?

No fix has been published for CVE-2019-14304 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-14304 being exploited?

There is no known exploitation of CVE-2019-14304 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2019-14301](https://insights.sbomify.com/CVE-2019-14301/): Information disclosure in n/a (high 7.5)
- [CVE-2019-14306](https://insights.sbomify.com/CVE-2019-14306/): Missing authorization in n/a (high 7.5)
- [CVE-2019-14302](https://insights.sbomify.com/CVE-2019-14302/): Security feature bypass in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-14304 and fix it if it is affected.

What it is: CVE-2019-14304 is a high-severity vulnerability in n/a, published on 10 Jan 2020. 
Exploitation: There is no known exploitation of CVE-2019-14304 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-14304/ (Markdown: https://insights.sbomify.com/CVE-2019-14304/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-14304
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-14304
- OSV: https://osv.dev/vulnerability/CVE-2019-14304

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-14304/
Summaries are generated and may contain mistakes; the official description above is the record.