dbcve.org
GitLabApplication

CVE-2020-13340

HIGH · 8.7 CVSS v3.1 Published 2020-10-08
Fix available
A fix is available. Upgrade to 13.2.10 / 13.3.7 or later.
See remediation →
91/100
Remediation priority · Urgent
High EPSS 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
An issue has been discovered in GitLab affecting all versions prior to 13.2.10, 13.3.7 and 13.4.2: Stored XSS in CI Job Log

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

Stored XSS vulnerability in GitLab's CI Job Log feature allows attackers to inject malicious JavaScript that executes when users view CI job logs. The vulnerability exists in all versions prior to 13.2.10, 13.3.7, and 13.4.2.

MitigationUpgrade GitLab to version 13.2.10, 13.3.7, 13.4.2 or later to patch the stored XSS in CI job logs.

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.2.10>= 13.3.0, < 13.3.7>= 13.4.0, < 13.4.2

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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-rake gitlab:env:info' or check /opt/gitlab/version file to retrieve the exact GitLab version number
    Affected if Version is below 13.2.10, or falls between 13.3.0-13.3.6 inclusive, or falls between 13.4.0-13.4.1 inclusive
  2. Confirm CI module is enabled
    Check that the GitLab CI/CD module is active by navigating to the Admin Area > Applications or running 'gitlab-ctl status' to verify gitlab-runner is configured
    Affected if CI/CD pipelines can be created or viewed in this GitLab instance
  3. Verify CI job log access exists
    Check for any existing CI pipelines with job logs by accessing a project with CI/CD enabled and viewing a job log page (typically at /-/jobs/:job_id)
    Affected if Users can access or view CI job log output in the GitLab instance

If the installed GitLab version falls within the affected ranges AND CI job logs are accessible to users, the environment is vulnerable to stored XSS in CI job logs.

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.2.10 / 13.3.7 / 13.4.2 or later
Fixed in 13.2.1013.3.713.4.2
Interim mitigation

Upgrade GitLab to version 13.2.10, 13.3.7, 13.4.2 or later to patch the stored XSS in CI job logs.

Fix this in GitLab Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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