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 pat...
Vendor
opentsdb vulnerabilities
7 published CVES affecting opentsdb, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 7
- Critical
- 4
- High
- 0
- Medium
- 3
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Products
Latest opentsdb CVEs
Newest publication first
-
CriticalCVSS 9.8 EPSS 16.5% Framework module Public exploit
-
MediumCVSS 6.1 EPSS 0.90%
Due to insufficient validation of parameters reflected in error messages by the legacy HTTP query API and the logging endpoint, it is possible to inject and execute malicious JavaScript within the browser of a targeted OpenTSDB user. This issue shares the same root cause as CVE-2...
-
CriticalCVSS 9.8 EPSS 43.0% Framework module Public exploit
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 vul...
-
CriticalCVSS 9.8 EPSS 85.3% Framework module Public exploit
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 attempte...
-
MediumCVSS 6.1 EPSS 0.67%
An issue was discovered in OpenTSDB 2.3.0. There is XSS in parameter 'type' to the /suggest URI.
-
MediumCVSS 6.1 EPSS 0.83%
An issue was discovered in OpenTSDB 2.3.0. There is XSS in parameter 'json' to the /q URI.
-
CriticalCVSS 9.8 EPSS 2.2%
An issue was discovered in OpenTSDB 2.3.0. Many parameters to the /q URI can execute commands, including o, key, style, and yrange and y2range and their JSON input.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.