Loading vulnerability…
OpenTSDB prior to version 2.4.2 is vulnerable to remote code execution due to improper handling of user-controlled input in the generation of Gnuplot configuration files. An attacker can inject arbitrary commands into the Gnuplot configuration, which are then executed when Gnuplot is run by the application, leading to arbitrary code execution on the server.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit module (modules/exploits/linux/http/opentsdb_key_cmd_injection.rb) that exploits an unauthenticated command injection vulnerability in OpenTSDB versions 2.4.1 and below (CVE-2023-36812, CVE-2023-25826). The exploit leverages the 'key' parameter in a graph plotting HTTP GET request to inject and execute arbitrary commands as root on the target system. The module first verifies the target is running a vulnerable version of OpenTSDB, then enumerates available metrics and aggregators, and finally delivers the payload via a crafted HTTP request. The default payload is a Meterpreter reverse shell, but any command payload supported by Metasploit can be used. The exploit is weaponized, requiring no authentication and providing reliable remote code execution. The only file in the repository is the Metasploit module itself, written in Ruby, and it is fully operational for use within the Metasploit framework.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.