LiveActive security incident?Get immediate response
CVE Record

CVE-2021-36230: HashiCorp Terraform Enterprise releases up to v202106-1 did not properly perform authorization checks on a...

HashiCorp Terraform Enterprise releases up to v202106-1 did not properly perform authorization checks on a subset of API requests executed using the run token, allowing privilege escalation to organization owner. Fixed in v202107-1.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Terraform Enterprise versions up to v202106-1 had an authorization flaw involving run tokens. A user or process able to use affected API requests could gain organization owner privileges. That level of access can affect infrastructure workflows and governance. HashiCorp states this was fixed in v202107-1.

Executive priority

Treat as high priority if Terraform Enterprise is used. Organization owner escalation can undermine control of infrastructure automation. Absence of known exploitation reduces emergency pressure, but affected systems should be upgraded promptly.

Technical view

The issue is improper authorization on a subset of Terraform Enterprise API requests executed with the run token. The documented impact is privilege escalation to organization owner. The provided sources do not include CVSS, CWE, detailed request scope, or proof-of-exploitation information.

Likely exposure

Exposure is limited to HashiCorp Terraform Enterprise releases up to v202106-1. Organizations not running Terraform Enterprise, or already on v202107-1 or later, are not indicated as affected by the supplied sources.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation. It only states that run-token API authorization failures could allow escalation to organization owner. No exploit maturity, prerequisites beyond run-token API context, or public exploit details are provided.

Researcher notes

Evidence is sparse. The public CVE text and HashiCorp advisory identify the impacted product range, run-token authorization context, impact, and fixed release. They do not provide CVSS scoring, affected CPEs, endpoint details, or exploitation status.

Mitigation direction

  • Upgrade Terraform Enterprise to v202107-1 or later.
  • Review the HashiCorp advisory for any deployment-specific guidance.
  • Identify deployments still running versions up to v202106-1.
  • Review organization owner membership for unexpected changes.
  • Confirm run-token handling follows current HashiCorp operational guidance.

Validation and detection

  • Check each Terraform Enterprise deployment version.
  • Verify remediated deployments report v202107-1 or later.
  • Review audit records for organization owner role changes.
  • Confirm no unsupported Terraform Enterprise releases remain in production.
  • Document exposure decisions for any unpatched legacy deployment.
Prepared
Confidence
medium
Sources
3

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
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior 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-2021-36230 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
3Source links

CVSS and timeline data

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

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.