LiveActive security incident?Get immediate response
CVE Record

CVE-2019-20933: InfluxDB before 1.7.6 has an authentication bypass vulnerability in the authenticate function in services/h...

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).

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

InfluxDB versions before 1.7.6 could incorrectly accept authentication involving a JWT shared secret that was empty. In practical terms, a database that operators believed was protected could be accessible without valid credentials under affected conditions.

Executive priority

Treat this as a high-priority remediation if InfluxDB is used for operational metrics, monitoring, or customer-adjacent data. The business risk is unauthorized access to time-series data that teams may assume is authenticated.

Technical view

The CVE describes an authentication bypass in InfluxDB's HTTP authentication path, specifically the authenticate function in services/httpd/handler.go. The issue is tied to JWT handling when the SharedSecret value is empty. The provided sources identify versions before 1.7.6 as affected and point to the 1.7.6 changeset and Debian security updates.

Likely exposure

Exposure is most likely where InfluxDB before 1.7.6 is deployed, especially if its HTTP API is reachable from users, services, VPNs, or the internet. Debian installations may also be affected until the referenced Debian security updates are applied.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. Public references include a GitHub issue, code changes, and Debian advisories, but no cited source here confirms exploitation in the wild.

Researcher notes

Evidence is concise but consistent: CVE text, upstream issue, upstream 1.7.6 comparison, a specific commit, and Debian advisories all identify an authentication bypass. The bundle lacks CVSS, CWE, detailed affected CPEs, and exploitation confirmation.

Mitigation direction

  • Upgrade InfluxDB to 1.7.6 or a later fixed release.
  • Apply Debian security updates from DLA-2501-1 or DSA-4823 where applicable.
  • Check vendor guidance before relying on configuration-only mitigation.
  • Restrict InfluxDB HTTP API access to trusted networks and required clients.
  • Review authentication and JWT shared secret configuration for unsafe empty values.

Validation and detection

  • Inventory all InfluxDB deployments and record exact versions.
  • Confirm no reachable deployment is running a version before 1.7.6.
  • For Debian systems, verify installed packages include the referenced security fixes.
  • Confirm the HTTP API still requires expected authentication after remediation.
  • Review access logs for unexpected database requests during the vulnerable period.
Prepared
Confidence
medium
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-20933 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.