dbcve.org
GitLabApplication

CVE-2019-14942

MEDIUM · 5.9 CVSS v3.1 Published 2023-04-16
Fix available
A fix is available. Upgrade to 11.11.8 / 12.0.6 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges 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
An issue was discovered in GitLab Community and Enterprise Edition before 11.11.8, 12 before 12.0.6, and 12.1 before 12.1.6. Cookies for GitLab Pages (which have access control) could be sent over cleartext HTTP.

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

GitLab Pages with access control was sending authentication cookies over cleartext HTTP instead of HTTPS. This allows network attackers to intercept cookies in transit, potentially gaining unauthorized access to private pages.

MitigationUpgrade GitLab to version 11.11.8, 12.0.6, or 12.1.6 or later, or ensure GitLab Pages is configured to only serve over HTTPS.

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:< 11.11.8>= 12.0.0, < 12.0.6>= 12.1.0, < 12.1.6

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/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 your installed GitLab version
    Run 'gitlab-rake gitlab:env:info' or check /opt/gitlab/version file to obtain the exact GitLab version installed
    Affected if Version is less than 11.11.8, or between 12.0.0-12.0.5, or between 12.1.0-12.1.5
  2. Verify if GitLab Pages is enabled
    Check the gitlab.rb configuration file for 'pages_external_url' setting or run 'gitlab-ctl show-config' to see if Pages is configured
    Affected if GitLab Pages is enabled and configured with an external URL
  3. Confirm Pages access control is enabled
    Check gitlab.rb for 'gitlab_pages['access_control'] = true' or examine the Pages configuration via the GitLab admin area under Pages settings
    Affected if Pages access control feature is turned on
  4. Inspect the Pages external URL protocol
    Review the 'pages_external_url' setting in gitlab.rb - look for http:// prefix rather than https://
    Affected if Pages external URL uses HTTP instead of HTTPS

You are affected if your GitLab version falls within the vulnerable ranges AND you have GitLab Pages with access control enabled serving over HTTP instead of HTTPS.

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 11.11.8 / 12.0.6 / 12.1.6 or later
Fixed in 11.11.812.0.612.1.6
Interim mitigation

Upgrade GitLab to version 11.11.8, 12.0.6, or 12.1.6 or later, or ensure GitLab Pages is configured to only serve over HTTPS.

Recommended fix High confidence

Upgrade to GitLab 11.11.8, 12.0.6, or 12.1.6 depending on your current major version branch

  1. Determine the current GitLab version using `sudo gitlab-rake gitlab:env:info` or checking the admin area UI
  2. If running a version before 11.11, upgrade directly to 11.11.8
  3. If running 12.0.x, upgrade to 12.0.6
  4. If running 12.1.x, upgrade to 12.1.6
  5. For GitLab installations using omnibus package: run `sudo apt-get update && sudo apt-get install gitlab-ce` (or `gitlab-ee`) to apply the update
  6. For source installations: follow the upgrade documentation for the specific version
  7. After upgrade, verify that GitLab Pages now properly enforces HTTPS for authenticated requests
Caveat Standard GitLab upgrade considerations apply; review the specific version release notes for any required migration steps or deprecated features

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

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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