# CVE-2020-16602: Race condition in n/a

> Remote attackers can execute arbitrary programs via a race condition in the Razer Chroma SDK Rest Server file handling process.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/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:** 2 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-gw77-j7h4-w4jv

## What is CVE-2020-16602?

CVE-2020-16602 is a high-severity vulnerability in n/a, published on 2 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Razer Chroma SDK Rest Server through 3.12.17 allows remote attackers to execute arbitrary programs because there is a race condition in which a file created under "%PROGRAMDATA%\Razer Chroma\SDK\Apps" can be replaced before it is executed by the server. The attacker must have access to port 54236 for a registration step.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2020-16602?

It affects 1 product.


Products: Razer Chroma Sdk.

## How do I fix CVE-2020-16602?

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

## Is CVE-2020-16602 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-16602 exists.

Public exploit code:

- Razer Chroma SDK Server 3.16.02 - Race Condition Remote File Execution (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-16602 and fix it if it is affected.

What it is: CVE-2020-16602 is a high-severity vulnerability in n/a, published on 2 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-16602 exists.

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-2020-16602/ (Markdown: https://insights.sbomify.com/CVE-2020-16602/index.md)
```

## Sources

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

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