dbcve.org
GitLabApplication

CVE-2020-13318

HIGH · 7.3 CVSS v3.1 Published 2020-09-14
Fix available
A fix is available. Upgrade to 13.0.12 / 13.1.10 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was discovered in GitLab versions before 13.0.12, 13.1.10, 13.2.8 and 13.3.4. GitLabs EKS integration was vulnerable to a cross-account assume role attack.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

GitLab's EKS integration contained a vulnerability allowing cross-account assume role attacks. This flaw in the AWS integration meant that an attacker with certain access could potentially assume IAM roles in other AWS accounts through the GitLab EKS integration feature.

MitigationUpgrade GitLab to version 13.0.12, 13.1.10, 13.2.8, or 13.3.4 or later to remediate the vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GitLabApplication
Affected:>= 13.0.0, < 13.0.12>= 13.1.0, < 13.1.10>= 13.2.0, < 13.2.8>= 13.3.0, < 13.3.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed GitLab version
    Run `gitlab-ctl version` on the GitLab server, or check the Admin Area > Settings > General page for the version number
    Affected if version is within 13.0.0 to 13.0.11, 13.1.0 to 13.1.9, 13.2.0 to 13.2.7, or 13.3.0 to 13.3.3
  2. Verify EKS integration is configured
    Check if any AWS EKS clusters have been integrated with this GitLab instance via Project Settings > Infrastructure > Kubernetes clusters or Admin Area > Kubernetes
    Affected if EKS integration is active and connected to AWS accounts
  3. Confirm AWS IAM role integration exists
    Review the Kubernetes cluster configurations for any IAM role trust relationships or AWS service account mappings configured in the GitLab Kubernetes integration settings
    Affected if IAM role assumptions are configured for Kubernetes service accounts

You are affected if your GitLab version falls within the affected ranges AND you have EKS integration with IAM role configurations enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 13.0.12 / 13.1.10 / 13.2.8 or later
Fixed in 13.0.1213.1.1013.2.8
Interim mitigation

Upgrade GitLab to version 13.0.12, 13.1.10, 13.2.8, or 13.3.4 or later to remediate the vulnerability.

Fix this in GitLab Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-13318 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-13318 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data