opentsdb vulnerabilities and fixes
Recent CVEs affecting opentsdb, with upgrade or downgrade steps. 2 tracked.
opentsdb has 2 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 2. Most recent: 2023-05-03. Highest priority: CVE-2023-25826 (score 72/100).
- CVE-2023-25827 HIGH 8.2 UPGRADE Due to insufficient validation of parameters reflected in error messages by the legacy HTTP query API and the
- CVE-2023-25826 CRITICAL 9.8 UPGRADE Due to insufficient validation of parameters passed to the legacy HTTP query API, it is possible to inject cra
FAQ
How do I fix opentsdb vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is opentsdb being exploited right now?
None of the tracked opentsdb CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which opentsdb CVE should I patch first?
CVE-2023-25826 currently ranks highest (72/100): Due to insufficient validation of parameters passed to the legacy HTTP query API, it is possible to inject cra.