# CVE-2022-43969: Hardcoded credentials in n/a

> Attackers can exploit mishandled credentials in Ricoh multifunction printers to gain unauthorized access and potentially read sensitive data.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Feb 2023
- **Updated:** 19 Mar 2025
- **Also known as:** GHSA-62wf-8699-486x

## What is CVE-2022-43969?

CVE-2022-43969 is a critical vulnerability in n/a, published on 16 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Ricoh mp_c4504ex devices with firmware 1.06 mishandle credentials.

Weakness: CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2022-43969?

It affects 77 products.


Products: Ricoh Im 2500 Firmware, Ricoh Im 2702 Firmware, Ricoh Im 3000 Firmware, Ricoh Im 3500 Firmware, Ricoh Im 350 Firmware, Ricoh Im 350f Firmware, Ricoh Im 4000 Firmware, Ricoh Im 430f Firmware, Ricoh Im 430fb Firmware, Ricoh Im 5000 Firmware, Ricoh Im 550f Firmware, Ricoh Im 6000 Firmware, Ricoh Im 600f Firmware, Ricoh Im 600srf Firmware, Ricoh Im 7000 Firmware, Ricoh Im 8000 Firmware, Ricoh Im 9000 Firmware, Ricoh Im C2000 Firmware, Ricoh Im C2500 Firmware, Ricoh Im C3000 Firmware and 57 more.

## How do I fix CVE-2022-43969?

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

## Is CVE-2022-43969 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-43969 and fix it if it is affected.

What it is: CVE-2022-43969 is a critical vulnerability in n/a, published on 16 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-43969 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-2022-43969/ (Markdown: https://insights.sbomify.com/CVE-2022-43969/index.md)
```

## Sources

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

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