influxdb vulnerabilities and fixes
Recent CVEs affecting influxdb, with upgrade or downgrade steps. 4 tracked.
influxdb has 4 tracked vulnerabilities, 2 critical. A fixed release or vendor patch exists for 4. Most recent: 2022-09-02. Highest priority: CVE-2019-20933 (score 69/100).
- CVE-2022-36640 CRITICAL 9.8 UPGRADE influxData influxDB before v1.8.10 contains no authentication mechanism or controls, allowing unauthenticated
- CVE-2019-20933 CRITICAL 9.8 UPGRADE MITIGATE InfluxDB before 1.7.6 has an authentication bypass vulnerability in the authenticate function in services/http
- CVE-2019-10329 HIGH 8.8 UPGRADE Jenkins InfluxDB Plugin 1.21 and earlier stored credentials unencrypted in its global configuration file on th
- CVE-2018-17572 MEDIUM 4.8 UPGRADE InfluxDB 0.9.5 has Reflected XSS in the Write Data module.
FAQ
How do I fix influxdb 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 influxdb being exploited right now?
None of the tracked influxdb CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which influxdb CVE should I patch first?
CVE-2019-20933 currently ranks highest (69/100): InfluxDB before 1.7.6 has an authentication bypass vulnerability in the authenticate function in services/http.