GHSA-hv53-q76c-7f8c
CRITICALGHSA-hv53-q76c-7f8c is a critical-severity (CVSS 9.8) OS Command Injection vulnerability in net.opentsdb:opentsdb. 3 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-hv53-q76c-7f8c is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
OS Command Injection in OpenTSDB
Blast Radius
net.opentsdb:opentsdbReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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.)
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | net.opentsdb:opentsdb | all versions | No fix |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
A remote code execution vulnerability occurs in OpenTSDB through 2.4.0 v…
A remote code execution vulnerability occurs in OpenTSDB through 2.4.0 v…
A remote code execution vulnerability occurs in OpenTSDB through 2.4.0 v…
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for net.opentsdb:opentsdb. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Remediation status
No patched version of net.opentsdb:opentsdb has shipped for GHSA-hv53-q76c-7f8c yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-hv53-q76c-7f8c is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-hv53-q76c-7f8c. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-hv53-q76c-7f8c in your dependencies?
O3 detects GHSA-hv53-q76c-7f8c across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.