Name | CVE-2022-36640 |
Description | influxData influxDB before v1.8.10 contains no authentication mechanism or controls, allowing unauthenticated attackers to execute arbitrary commands. NOTE: the CVE ID assignment is disputed because the vendor's documentation states "If InfluxDB is being deployed on a publicly accessible endpoint, we strongly recommend authentication be enabled. Otherwise the data will be publicly available to any unauthenticated user. The default settings do NOT enable authentication and authorization. |
Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
Vulnerable and fixed packages
The table below lists information on source packages.
Source Package | Release | Version | Status |
---|
influxdb (PTS) | stretch (security), stretch (lts), stretch | 1.1.1+dfsg1-4+deb9u1 | vulnerable |
| buster (security), buster, buster (lts) | 1.6.4-1+deb10u1 | vulnerable |
| bullseye, bookworm | 1.6.7~rc0-1 | vulnerable |
| sid, trixie | 1.6.7~rc0-2 | vulnerable |
The information below is based on the following data on fixed versions.
Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
---|
influxdb | source | (unstable) | (unfixed) | unimportant | | |
Notes
If InfluxDB is deployed on publicly accessible endpoint, it is recommended
to enable authentication.