CVE-2019-20933: Improper Authentication in InfluxDB
Summary
CVE-2019-20933: Improper Authentication in InfluxDB. Affects github.com/influxdata/influxdb versions < 1.7.6. Fixed in 1.7.6. How to fix ↓
Also tracked for
- influxdb · Debian:11
The same CVE-2019-20933 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
InfluxDB is a popular open-source time series database designed to handle high write and query loads. It provides a scalable and efficient solution for storing and analyzing time-stamped data. The affected package, github.com/influxdata/influxdb/services/httpd, is responsible for handling HTTP requests in InfluxDB. This vulnerability allows an attacker to bypass authentication by exploiting an issue in the authenticate function. Specifically, a JSON Web Token (JWT) token with an empty SharedSecret can be used to authenticate without a valid secret. This vulnerability has a critical severity rating and is assigned CVE-2019-20933.
Vulnerability Detail
The vulnerability in InfluxDB allows an attacker to bypass authentication and gain unauthorized access to the database. By providing a JWT token with an empty SharedSecret, the attacker can trick the authenticate function into granting access without a valid secret. This can lead to unauthorized data access, modification, or deletion. The vulnerability is critical, with a CVSS v3 score of 9.8, indicating a high level of severity. It affects InfluxDB versions prior to 1.7.6.
How To Fix
Latest published version: v1.13.1 as of 22 Oct 2026
go get github.com/influxdata/influxdb@v1.13.1
Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
1.7.6
This is the first release that contains the fix.
go get github.com/influxdata/influxdb@v1.7.6
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
As a temporary workaround, users can disable authentication in InfluxDB. However, this is not recommended as it leaves the database exposed to unauthorized access. To disable authentication, modify the configuration file and set the auth-enabled option to false. Restart the InfluxDB service for the changes to take effect. It is strongly advised to apply the official fix by upgrading to a patched version.
Conclusion
InfluxDB before version 1.7.6 is vulnerable to an authentication bypass issue that allows unauthorized access to the database. It is crucial to upgrade to the latest version to mitigate this vulnerability. Disabling authentication as a temporary workaround is not recommended. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for github.com/influxdata/influxdb →
FAQ
InfluxDB is an open-source time series database designed for handling high write and query loads. It provides a scalable and efficient solution for storing and analyzing time-stamped data.
The vulnerability allows an attacker to bypass authentication and gain unauthorized access to the InfluxDB database. This can lead to unauthorized data access, modification, or deletion.
To fix this vulnerability, it is recommended to upgrade to InfluxDB version 1.7.6 or later. Upgrade instructions can be found in the official InfluxDB documentation.
Yes, you can disable authentication in InfluxDB as a temporary workaround. However, this is not recommended as it leaves the database exposed to unauthorized access. It is strongly advised to apply the official fix by upgrading to a patched version.
This vulnerability has a critical severity rating, with a CVSS v3 score of 9.8, indicating a high level of severity.
References
Related vulnerabilities
Recent vulnerabilities recorded for github.com/influxdata/influxdb.