dbcve.org
GitLabApplication

CVE-2019-19628

CRITICAL · 9.8 CVSS v3.1 Published 2020-01-05
Fix available
A fix is available. Upgrade to after 12.5.3 or later.
See remediation →
100/100
Remediation priority · Urgent
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
In GitLab EE 11.3 through 12.5.3, 12.4.5, and 12.3.8, insufficient parameter sanitization for the Maven package registry could lead to privilege escalation and remote code execution vulnerabilities under certain conditions.

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

This GitLab EE vulnerability stems from improper input validation in the Maven package registry functionality. An attacker could exploit insufficient parameter sanitization to perform privilege escalation and achieve remote code execution on the GitLab server. The 'certain conditions' mentioned likely involve authenticated access to the Maven registry feature.

MitigationUpgrade GitLab EE to a version beyond 12.5.3 (or 12.4.5/12.3.8) that contains the fix, and review Maven repository access controls to limit exposure until patching is complete.

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.3.0, <= 12.3.8>= 12.4.0, <= 12.4.5>= 12.5.0, <= 12.5.3

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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. Identify installed GitLab version
    Run `gitlab-rake gitlab:version` or check the GitLab admin panel under Help > Version to determine the exact installed version
    Affected if Version is 11.3.0 through 12.3.8, 12.4.0 through 12.4.5, or 12.5.0 through 12.5.3
  2. Confirm Maven registry is enabled
    Navigate to Admin Area > Settings > Maven Settings, or check if any projects have Maven packages enabled under Packages & Registries > Maven Registry
    Affected if Maven registry feature is enabled and accessible to authenticated users
  3. Review Maven repository access controls
    Check project-level and group-level Maven registry permissions to see which users have write or read access to Maven packages
    Affected if Authenticated users with Maven registry access exist in the instance

Your GitLab instance is affected if it runs a version between 11.3.0 and 12.5.3 AND has the Maven registry feature enabled with authenticated users able to access it

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

Upgrade GitLab EE to a version beyond 12.5.3 (or 12.4.5/12.3.8) that contains the fix, and review Maven repository access controls to limit exposure until patching is complete.

Recommended fix High confidence

GitLab 12.5.4 or later (or the next patched release in your minor branch: 12.3.9 for 12.3.x, 12.4.6 for 12.4.x)

  1. Identify your current GitLab installation version using `sudo gitlab-rake gitlab:env:info`
  2. Ensure you have a complete backup of your GitLab instance including database and repositories
  3. Review GitLab upgrade documentation for your specific version path
  4. Upgrade to the appropriate patched version: If on 11.3.x-12.3.x, upgrade to 12.3.9 or later; If on 12.4.x, upgrade to 12.4.6 or later; If on 12.5.x, upgrade to 12.5.4 or later
  5. After upgrade, verify the Maven package registry functionality works correctly
  6. Confirm the upgrade using `sudo gitlab-rake gitlab:env:info` to ensure the new version is running
Caveat Major version upgrades may require database migrations and downtime; review GitLab upgrade path documentation for required intermediate upgrades if moving across multiple major versions

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

Fix this in GitLab Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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