LiveActive security incident?Get immediate response
CVE Record

CVE-2022-36640: influxData influxDB before v1.8.10 contains no authentication mechanism or controls, allowing unauthenticat...

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

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This CVE claims older InfluxDB deployments before 1.8.10 may allow unauthenticated attackers to execute arbitrary commands. The record is disputed: vendor documentation says authentication is intentionally disabled by default unless administrators enable it. The main business risk is an exposed InfluxDB service running without authentication.

Executive priority

Prioritize discovery and exposure reduction over emergency exploitation response. Public unauthenticated database access can create serious operational and data risk, but the supplied evidence does not confirm active exploitation or a vendor-accepted vulnerability.

Technical view

The CVE record describes missing authentication controls in InfluxDB before v1.8.10, with claimed unauthenticated command execution. Evidence is limited and disputed because InfluxData documents that default deployments do not enable authentication or authorization, especially warning against public exposure without enabling auth.

Likely exposure

Exposure is most likely where InfluxDB is reachable from public or untrusted networks and authentication was not enabled. The provided affected-product metadata is incomplete, listing n/a values.

Exploitation context

The source bundle does not show CISA KEV listing, confirmed active exploitation, CVSS scoring, or a vendor advisory confirming exploitation. Treat exploitation status as unconfirmed.

Researcher notes

The CVE is disputed and lacks CVSS, CWE, precise affected CPEs, and a clear vendor advisory. Research should distinguish insecure default or deployment configuration from a software vulnerability before assigning remediation ownership.

Mitigation direction

  • Inventory InfluxDB deployments and identify versions before 1.8.10.
  • Restrict InfluxDB access to trusted networks only.
  • Enable authentication and authorization for any reachable deployment.
  • Review InfluxData guidance before assuming this is a vendor-confirmed flaw.
  • Evaluate upgrade options using official InfluxData downloads.

Validation and detection

  • Confirm no InfluxDB endpoint is publicly reachable without business need.
  • Verify authentication is enabled on every exposed InfluxDB instance.
  • Document deployed InfluxDB versions and compare with the CVE boundary.
  • Review access logs for unexpected unauthenticated access.
  • Track vendor documentation for clarification because the CVE is disputed.
Prepared
Confidence
medium
Sources
5

Public sources used

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.

cve · low confidence lookup

CVE-2022-36640 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
3Timeline events
1ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container

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.