CVE-2019-20933

CRITICALNVD 9.89.8
EchelonGraph scoreLOW confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: nvd
Elevated
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 31%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

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

CVSS v3
9.8
EG Score
9.8(low)
EPSS
98.0%
KEV
Not listed

Published

November 19, 2020

Last Modified

November 21, 2024

Advisory Details (5)

Auto-updated Jun 22, 2026
Patch available. Sources: github_commit.
generic

[SECURITY] [DSA 4823-1] influxdb security update

https://www.debian.org/security/2021/dsa-4823
generic Patch Available

[SECURITY] [DLA 2501-1] influxdb security update

https://lists.debian.org/debian-lts-announce/2020/12/msg00030.html
generic

Password bypass vulnerability · Issue #12927 · influxdata/influxdb · GitHub

https://github.com/influxdata/influxdb/issues/12927
generic

Comparing v1.7.5...v1.7.6 · influxdata/influxdb · GitHub

https://github.com/influxdata/influxdb/compare/v1.7.5...v1.7.6
github_commit

commit 761b557315ff (influxdata/influxdb)

Fix landed in influxdata/influxdb commit 761b557315ff — awaiting tagged release

https://github.com/influxdata/influxdb/commit/761b557315ff9c1642cf3b0e5797cd3d983a24c0

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuinfluxdb-client (1.6.4-1+deb10u1build0.20.04.1) @ focal2026-05-23ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/influxdata/influxdb—1.7.6—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 8× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-12 05:43 UTCEPSS rescore
  2. 2026-07-12 05:43 UTCEPSS rescore
  3. 2026-07-11 08:24 UTCEPSS rescore
  4. 2026-07-11 08:24 UTCEPSS rescore
  5. 2026-07-09 19:06 UTCEPSS rescore
  6. 2026-07-08 15:11 UTCEPSS rescore
  7. 2026-07-06 16:25 UTCEPSS rescore
  8. 2026-07-06 16:25 UTCEPSS rescore
  9. 2026-07-04 06:28 UTCEPSS rescore
  10. 2026-07-01 15:03 UTCEPSS rescore
  11. 2026-07-01 15:03 UTCEPSS rescore
  12. 2026-06-28 04:54 UTCEPSS rescore
  13. 2026-06-28 04:54 UTCEPSS rescore
  14. 2026-06-27 03:06 UTCEPSS rescore
  15. 2026-06-25 13:47 UTCEPSS rescore
  16. 2026-06-25 13:47 UTCEPSS rescore
  17. 2026-06-24 14:03 UTCEPSS rescore
  18. 2026-06-24 14:03 UTCEPSS rescore
  19. 2026-06-24 08:50 UTCOSV refresh
  20. 2026-06-23 21:31 UTCEPSS rescore
  21. 2026-06-23 21:30 UTCEPSS rescore
  22. 2026-06-22 14:23 UTCEPSS rescore
  23. 2026-06-21 01:57 UTCEPSS rescore
  24. 2026-06-21 01:57 UTCEPSS rescore
  25. 2026-06-18 17:50 UTCEPSS rescore
Show 17 more
  1. 2026-06-17 17:50 UTCEPSS rescore
  2. 2026-06-16 17:50 UTCEPSS rescore
  3. 2026-06-15 17:45 UTCEPSS rescore
  4. 2026-06-14 23:15 UTCEPSS rescore
  5. 2026-06-14 23:15 UTCEPSS rescore
  6. 2026-06-10 13:19 UTCEPSS rescore
  7. 2026-06-07 12:29 UTCOSV refresh
  8. 2026-06-04 13:10 UTCEPSS rescore
  9. 2026-06-04 13:10 UTCEPSS rescore
  10. 2026-05-31 22:29 UTCEPSS rescore
  11. 2026-05-31 22:29 UTCEPSS rescore
  12. 2026-05-29 13:42 UTCEPSS rescore
  13. 2026-05-26 07:17 UTCEPSS rescore
  14. 2026-05-26 07:17 UTCEPSS rescore
  15. 2026-05-26 07:17 UTCEPSS rescore
  16. 2026-05-23 05:03 UTCEG score recompute
  17. 2026-05-23 05:03 UTCVendor advisory

Publicly available exploits

(3 references)

Working exploit code is in the public domain (2 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCHydragyrum/CVE-2019-20933
    First seen Jul 24, 2021
    Open source ↗
  • GitHub PoCLorenzoTullini/InfluxDB-Exploit-CVE-2019-20933
    First seen Apr 28, 2021

    InfluxDB CVE-2019-20933 vulnerability exploit

    Open source ↗
  • Nucleihttp/cves/2019/CVE-2019-20933.yaml
    First seen Jan 1, 2019

    InfluxDB <1.7.6 - Authentication Bypass

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2019-20933?
CVE-2019-20933 is a critical vulnerability published on November 19, 2020. 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).
When was CVE-2019-20933 disclosed?
CVE-2019-20933 was first published in the National Vulnerability Database on November 19, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-20933 actively exploited?
CVE-2019-20933 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-20933?
CVE-2019-20933 has a CVSS v3 base score of 9.8 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2019-20933?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-20933, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-20933

Explore →

Is Your Infrastructure Affected by CVE-2019-20933?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs