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

> Attackers can execute arbitrary OS commands on OpenTSDB hosts via the legacy HTTP query API due to insufficient input validation.

- **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:** 3 May 2023
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-h475-7v3c-26q7

## What is CVE-2023-25826?

CVE-2023-25826 is a critical command injection vulnerability in OpenTSDB, published on 3 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Due to insufficient validation of parameters passed to the legacy HTTP query API, it is possible to inject crafted OS commands into multiple parameters and execute malicious code on the OpenTSDB host system. This exploit exists due to an incomplete fix that was made when this vulnerability was previously disclosed as CVE-2020-35476. Regex validation that was implemented to restrict allowed input to the query API does not work as intended, allowing crafted commands to bypass validation.

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

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

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.1 | None |
| `net.opentsdb:opentsdb` | Maven | All versions to 2.4.1 | None |

Products: Opentsdb Opentsdb.

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

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

## Is CVE-2023-25826 being exploited?

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

Public exploit code:

- OpenTSDB 2.4.1 unauthenticated command injection (metasploit)
- OpenTSDB <= 2.4.1 - Unauthenticated RCE via Gnuplot Injection (nuclei): http/cves/2023/CVE-2023-25826.yaml

## Other vulnerabilities in OpenTSDB

- [CVE-2023-36812](https://insights.sbomify.com/CVE-2023-36812/): 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-25826 and fix it if it is affected.

What it is: CVE-2023-25826 is a critical command injection vulnerability in OpenTSDB, published on 3 May 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-25826 exists.

Affected packages and fixed versions:
- net.opentsdb:opentsdb (Maven): affected all versions up to 2.4.1; no fix listed
- net.opentsdb:opentsdb (Maven): affected all versions up to 2.4.1; 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-2023-25826/ (Markdown: https://insights.sbomify.com/CVE-2023-25826/index.md)
```

## Sources

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

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