# CVE-2024-36480: Hardcoded credentials in Ricoh Streamline NX PC Client

> Hard-coded credentials in Ricoh Streamline NX PC Client allow attackers to gain LocalSystem privileges and execute unintended operations on the host PC.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jun 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-f96p-2mg2-2p89

## What is CVE-2024-36480?

CVE-2024-36480 is a critical vulnerability in CVE-2024-36480 Ricoh Streamline NX PC Client, published on 19 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Use of hard-coded credentials issue exists in Ricoh Streamline NX PC Client ver.3.7.2 and earlier. If this vulnerability is exploited, an attacker may obtain LocalSystem Account of the PC where the product is installed. As a result, unintended operations may be performed on the PC.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2024-36480?


## How do I fix CVE-2024-36480?

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

## Is CVE-2024-36480 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-36480 and fix it if it is affected.

What it is: CVE-2024-36480 is a critical vulnerability in CVE-2024-36480 Ricoh Streamline NX PC Client, published on 19 Jun 2024. 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-2024-36480 in the wild and no public exploit code.

Affected product: CVE-2024-36480 Ricoh Streamline NX PC Client. 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-2024-36480/ (Markdown: https://insights.sbomify.com/CVE-2024-36480/index.md)
```

## Sources

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

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