dbcve.org
GitLabApplication

CVE-2020-13347

CRITICAL · 9.1 CVSS v3.1 Published 2020-10-07
Fix available
A fix is available. Upgrade to 13.2.4 / 13.3.2 or later.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 command injection vulnerability was discovered in Gitlab runner versions prior to 13.2.4, 13.3.2 and 13.4.1. When the runner is configured on a Windows system with a docker executor, which allows the attacker to run arbitrary commands on Windows host, via DOCKER_AUTH_CONFIG build variable.

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 · high confidence

Command injection vulnerability in GitLab Runner on Windows systems with docker executor. The DOCKER_AUTH_CONFIG build variable is not properly sanitized, allowing attackers to inject arbitrary commands that execute on the Windows host system with the privileges of the GitLab Runner service.

MitigationUpgrade GitLab Runner to version 13.2.4, 13.3.2, or 13.4.1 or later. As a defense-in-depth measure, restrict who can modify CI/CD pipeline variables and consider using GitLab's protected variables feature.

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:>= 12.0.0, < 13.2.4>= 13.3.0, < 13.3.2>= 13.4.0, < 13.4.1

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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

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 GitLab Runner version
    Run 'gitlab-runner --version' to get the installed version number.
    Affected if The version falls within: 12.0.0 to 13.2.3, 13.3.0 to 13.3.1, or 13.4.0.
  2. Confirm Windows operating system
    Check the OS where GitLab Runner is installed using 'systeminfo' or 'winver'.
    Affected if The runner operates on Windows; this vulnerability only affects Windows systems.
  3. Verify docker executor is in use
    Inspect the GitLab Runner configuration file (config.toml) and look for the 'executor' setting under each runner section.
    Affected if The executor is set to 'docker'.
  4. Identify DOCKER_AUTH_CONFIG usage
    Review CI/CD pipeline YAML files and runner configuration for presence of the DOCKER_AUTH_CONFIG variable, which may be set as a CI/CD variable or in config.toml.
    Affected if DOCKER_AUTH_CONFIG build variable is defined and used in pipelines.

A user is affected if GitLab Runner version is vulnerable (12.0.0-13.2.3, 13.3.0-13.3.1, or 13.4.0-13.4.1), running on Windows with docker executor, and DOCKER_AUTH_CONFIG is utilized as a build variable.

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.

dbcve · scoped
Upgrade available Upgrade to 13.2.4 / 13.3.2 / 13.4.1 or later
Fixed in 13.2.413.3.213.4.1
Interim mitigation

Upgrade GitLab Runner to version 13.2.4, 13.3.2, or 13.4.1 or later. As a defense-in-depth measure, restrict who can modify CI/CD pipeline variables and consider using GitLab's protected variables feature.

Recommended fix High confidence

GitLab Runner 13.2.4, 13.3.2, 13.4.1, or later stable release

  1. Identify the current GitLab Runner version using `gitlab-runner --version`
  2. Download the appropriate fixed GitLab Runner version (13.2.4, 13.3.2, or 13.4.1, or a later stable version) from the official GitLab Runner releases
  3. Stop the GitLab Runner service using `sudo gitlab-runner stop` or `gitlab-runner stop`
  4. Install the upgraded GitLab Runner package for your operating system
  5. Restart the GitLab Runner service using `sudo gitlab-runner start` or `gitlab-runner start`
  6. Verify the upgrade was successful by checking the version with `gitlab-runner --version`
Caveat Review GitLab Runner release notes for breaking changes between your current version and the target version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in GitLab Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,960
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,736.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-13347 — 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-13347 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