golang-github-influxdb-influxdb-dev: InfluxDB before 1.7.6 has an authentication bypass vulnerability in the authenticate function in services/httpd/handl...
CVE-2019-20933 is fixed in 3 products on 1 platform, first by golang-github-influxdb-influxdb-dev 1.1.1+dfsg1-4+deb9u1ubuntu1, released November 18, 2020. It is not reported as exploited. Patch Radar priority: Routine.
InfluxDB before 1.7.6 has an authentication bypass vulnerability in the authenticate function in services/httpd/handler.go because a JWT token may have an empty SharedSecret (aka shared secret).
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| golang-github-influxdb-influxdb-dev · Ubuntu 18.04.6 LTS (bionic) | 1.1.1+dfsg1-4+deb9u1ubuntu1 | golang-github-influxdb-influxdb-dev 1.1.1+dfsg1-4+deb9u1ubuntu1 | Nov 18, 2020 |
| golang-github-influxdb-influxdb-dev · Ubuntu 20.04 LTS (focal) | 1.6.4-1+deb10u1build0.20.04.1 | golang-github-influxdb-influxdb-dev 1.6.4-1+deb10u1build0.20.04.1 | Nov 18, 2020 |
| golang-github-influxdb-influxdb-dev · Ubuntu 22.04.1 LTS (jammy) | 1.6.7~rc0-1 | golang-github-influxdb-influxdb-dev 1.6.7~rc0-1 | Nov 18, 2020 |
| influxdb · Ubuntu 18.04.6 LTS (bionic) | 1.1.1+dfsg1-4+deb9u1ubuntu1 | influxdb 1.1.1+dfsg1-4+deb9u1ubuntu1 | Nov 18, 2020 |
| influxdb · Ubuntu 20.04 LTS (focal) | 1.6.4-1+deb10u1build0.20.04.1 | influxdb 1.6.4-1+deb10u1build0.20.04.1 | Nov 18, 2020 |
| influxdb · Ubuntu 22.04.1 LTS (jammy) | 1.6.7~rc0-1 | influxdb 1.6.7~rc0-1 | Nov 18, 2020 |
| influxdb-client · Ubuntu 18.04.6 LTS (bionic) | 1.1.1+dfsg1-4+deb9u1ubuntu1 | influxdb-client 1.1.1+dfsg1-4+deb9u1ubuntu1 | Nov 18, 2020 |
| influxdb-client · Ubuntu 20.04 LTS (focal) | 1.6.4-1+deb10u1build0.20.04.1 | influxdb-client 1.6.4-1+deb10u1build0.20.04.1 | Nov 18, 2020 |
| influxdb-client · Ubuntu 22.04.1 LTS (jammy) | 1.6.7~rc0-1 | influxdb-client 1.6.7~rc0-1 | Nov 18, 2020 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.