# CVE-2020-35476: OS Command Injection in OpenTSDB

> Attackers can execute arbitrary commands on OpenTSDB servers via the yrange parameter, leading to remote code execution.

- **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:** 16 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-hv53-q76c-7f8c

## What is CVE-2020-35476?

CVE-2020-35476 is a critical command injection vulnerability in n/a, published on 16 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A remote code execution vulnerability occurs in OpenTSDB through 2.4.0 via command injection in the yrange parameter. The yrange value is written to a gnuplot file in the /tmp directory. This file is then executed via the mygnuplot.sh shell script. (tsd/GraphHandler.java attempted to prevent command injections by blocking backticks but this is insufficient.)

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

2 open source packages ship an affected version, including net.opentsdb:opentsdb. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `net.opentsdb:opentsdb` | Maven | All versions to 2.4.0 | None |
| `net.opentsdb:opentsdb` | Maven | All versions to 2.4.0 | None |

Products: Opentsdb Opentsdb.

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

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

## Is CVE-2020-35476 being exploited?

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

Public exploit code:

- A remote code execution vulnerability occurs in OpenTSDB through 2.4.0 via command injection in the yrange parameter.  (github_poc): https://github.com/glowbase/CVE-2020-35476
- OpenTSDB 2.4.0 unauthenticated command injection (metasploit)
- Vulhub opentsdb/CVE-2020-35476: OpenTSDB Gnuplot Command Injection (CVE-2020-35476), run with Isoloom (github_poc): https://github.com/CyberCTF/vulhub-opentsdb-cve-2020-35476
- OpenTSDB <=2.4.0 - Remote Code Execution (nuclei): http/cves/2020/CVE-2020-35476.yaml

## Other vulnerabilities in n/a

- [CVE-2023-36812](https://insights.sbomify.com/CVE-2023-36812/): Remote Code Execution in OpenTSDB (critical 9.8)
- [CVE-2023-25826](https://insights.sbomify.com/CVE-2023-25826/): Remote Code Execution in OpenTSDB (critical 9.8)
- [CVE-2018-12972](https://insights.sbomify.com/CVE-2018-12972/): OpenTSDB vulnerable to OS Command Injection (critical 9.8)
- [CVE-2023-25827](https://insights.sbomify.com/CVE-2023-25827/): Cross-site Scripting in OpenTSDB (high 8.2)
- [CVE-2018-12973](https://insights.sbomify.com/CVE-2018-12973/): OpenTSDB Cross-site Scripting vulnerability (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-35476 is a critical command injection vulnerability in n/a, published on 16 Dec 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-35476 exists.

Affected packages and fixed versions:
- net.opentsdb:opentsdb (Maven): affected all versions up to 2.4.0; no fix listed
- net.opentsdb:opentsdb (Maven): affected all versions up to 2.4.0; no fix listed

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

## Sources

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

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