# CVE-2023-36812: Remote Code Execution in OpenTSDB

> Attackers can execute arbitrary code by injecting commands into Gnuplot configuration files within OpenTSDB.

- **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:** Yes
- **Published:** 30 Jun 2023
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-76f7-9v52-v2fw

## What is CVE-2023-36812?

CVE-2023-36812 is a critical command injection vulnerability in opentsdb, published on 30 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenTSDB is a open source, distributed, scalable Time Series Database (TSDB). OpenTSDB is vulnerable to Remote Code Execution vulnerability by writing user-controlled input to Gnuplot configuration file and running Gnuplot with the generated configuration. This issue has been patched in  commit `07c4641471c` and further refined in commit `fa88d3e4b`. These patches are available in the `2.4.2` release. Users are advised to upgrade. User unable to upgrade may disable Gunuplot via the config option`tsd.core.enable_ui = true` and remove the shell files `mygnuplot.bat` and `mygnuplot.sh`.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2023-36812?

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 | 2.4.2 |
| `net.opentsdb:opentsdb` | Maven | All versions | 2.4.2 |

Products: Opentsdb Opentsdb.

## How do I fix CVE-2023-36812?

Upgrade net.opentsdb:opentsdb to 2.4.2 or later.

## Is CVE-2023-36812 being exploited?

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

Public exploit code:

- An exploit for OpenTSDB <= 2.4.1 cmd injection (CVE-2023-36812/CVE-2023-25826) written in Fortran (github_poc): https://github.com/ErikWynter/opentsdb_key_cmd_injection
- OpenTSDB 2.4.1 unauthenticated command injection (metasploit)

## Other vulnerabilities in opentsdb

- [CVE-2023-25826](https://insights.sbomify.com/CVE-2023-25826/): Remote Code Execution in OpenTSDB (critical 9.8)
- [CVE-2020-35476](https://insights.sbomify.com/CVE-2020-35476/): OS Command Injection 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-2023-36812 and fix it if it is affected.

What it is: CVE-2023-36812 is a critical command injection vulnerability in opentsdb, published on 30 Jun 2023. 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-2023-36812 exists.

Affected packages and fixed versions:
- net.opentsdb:opentsdb (Maven): affected all versions; fixed in 2.4.2
- net.opentsdb:opentsdb (Maven): affected all versions; fixed in 2.4.2

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

## Sources

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

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