dbcve.org
GitLabApplication

CVE-2020-10075

MEDIUM · 6.1 CVSS v3.1 Published 2020-03-13
Fix available
A fix is available. Upgrade to after 12.8.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
GitLab 12.5 through 12.8.1 allows HTML Injection. A particular error header was potentially susceptible to injection or potentially other vulnerabilities via unescaped input.

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

HTML Injection vulnerability in GitLab 12.5 through 12.8.1 where an error header does not properly escape user-controlled input, allowing injection of malicious HTML content into the header response.

MitigationUpgrade to GitLab 12.8.2 or later, and implement proper output encoding/escaping of all user input before including it in HTTP headers.

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.5.0, <= 12.8.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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Identify installed GitLab version
    Access the GitLab admin area and navigate to the version information page, or use the API endpoint GET /api/v4/version, or run the command 'gitlab-rake gitlab:env:info' from the GitLab server console
    Affected if The version displayed is between 12.5.0 and 12.8.1 inclusive
  2. Confirm version number format
    Verify the exact version string shown matches the affected range (e.g., 12.5.0, 12.5.1, 12.6.0, 12.7.0, 12.8.0, or 12.8.1)
    Affected if The displayed version exactly matches one of the versions in the 12.5.0 to 12.8.1 range
  3. Determine if GitLab web interface is accessible
    Verify that the GitLab instance is running and the web interface or API endpoints are reachable over HTTP/HTTPS
    Affected if The web interface is accessible and the vulnerable error header code path can be triggered by user input

You are affected if your installed GitLab version is 12.5.0, 12.5.1, 12.6.0, 12.6.1, 12.6.2, 12.7.0, 12.7.1, 12.8.0, or 12.8.1 and the application processes user-controlled input into error headers.

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 a release after 12.8.1
Interim mitigation

Upgrade to GitLab 12.8.2 or later, and implement proper output encoding/escaping of all user input before including it in HTTP headers.

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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