LiveActive security incident?Get immediate response
CVE Record

CVE-2020-13359: The Terraform API in GitLab CE/EE 12.10+ exposed the object storage signed URL on the delete operation allo...

The Terraform API in GitLab CE/EE 12.10+ exposed the object storage signed URL on the delete operation allowing a malicious project maintainer to overwrite the Terraform state, bypassing audit and other business controls. Affected versions are >=12.10, <13.3.9,>=13.4, <13.4.5,>=13.5, <13.5.2.

HighCVSS 7.6Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This GitLab flaw let a project maintainer obtain a signed object-storage URL during a Terraform state delete operation. That could allow Terraform state to be overwritten outside normal audit and business controls. The issue matters most where Terraform state is used for production infrastructure decisions.

Executive priority

Prioritize remediation where GitLab stores Terraform state for sensitive infrastructure. The vulnerability needs maintainer-level access, but a successful abuse could undermine infrastructure change controls and audit confidence.

Technical view

GitLab CE/EE Terraform API versions 12.10 through the listed vulnerable ranges exposed an object storage signed URL on delete operations. With project maintainer privileges, an attacker could overwrite Terraform state, producing high integrity impact across scope boundaries with low complexity and no user interaction.

Likely exposure

Exposure is limited to GitLab CE/EE instances in affected versions: >=12.10 <13.3.9, >=13.4 <13.4.5, or >=13.5 <13.5.2, especially projects using GitLab-managed Terraform state with object storage.

Exploitation context

The source bundle does not show CISA KEV listing or public active exploitation. Abuse requires high privileges: a malicious or compromised project maintainer account. The main risk is unauthorized Terraform state tampering with reduced audit visibility.

Researcher notes

The available sources define affected versions, privilege requirement, and impact, but do not provide exploit evidence or detailed remediation beyond fixed version boundaries. Focus validation on version exposure, Terraform state usage, object storage configuration, and maintainer access governance.

Mitigation direction

  • Upgrade GitLab CE/EE to a version outside the affected ranges.
  • Prioritize projects using GitLab Terraform state backed by object storage.
  • Review and reduce project Maintainer access where not required.
  • Check GitLab vendor guidance before applying compensating controls.
  • Treat suspicious Terraform state changes as potential integrity incidents.

Validation and detection

  • Inventory GitLab CE/EE versions across self-managed instances.
  • Identify projects using GitLab-managed Terraform state and object storage.
  • Review project Maintainer membership for unnecessary or compromised accounts.
  • Look for unexpected Terraform state changes or state drift.
  • Confirm upgraded instances are not in the affected version ranges.
Prepared
Confidence
high
Sources
4

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-2020-13359 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
High
CVSS
7.6 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:H/A:N

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.6CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:H/A:N2.34.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.6High
CVSS 3.1 vector shape for CVE-2020-13359Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GitLabGitLab CE/EE>=12.10, <13.3.9, >=13.4, <13.4.5, >=13.5, <13.5.2Listed
Weakness

CWE details

No CWE listed

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