GitLabApplication
CVE-2019-19256
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 · uneditedGitLab Enterprise Edition (EE) 12.2 and later through 12.5 has Incorrect Access Control.
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 confidenceGitLab Enterprise Edition versions 12.2 through 12.5 contains an Incorrect Access Control vulnerability that allows unauthorized access to certain resources or functionality due to improper authorization checks.
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
>= 12.2.0, < 12.5.1CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed GitLab versionNavigate to the GitLab Admin Area (Admin > Overview > Dashboard) and locate the version number displayed on the main dashboard, or run the command `gitlab-rake gitlab:env:info` on the server to retrieve version detailsAffected if The displayed version falls within the range 12.2.0 to 12.5.0 (any version less than 12.5.1)
-
Confirm the GitLab edition is Enterprise EditionCheck the Admin Area dashboard or the output of `gitlab-rake gitlab:env:info` to verify the edition is listed as 'GitLab Enterprise Edition' rather than Community EditionAffected if The edition is GitLab Enterprise Edition and the version meets the affected range criterion
-
Verify the specific minor versionIf the version shows 12.2.x, 12.3.x, 12.4.x, or 12.5.0, this confirms the installation is within the affected version range. The exact version can also be checked by examining the GitLab package or running `cat /opt/gitlab/version-manifest.json`Affected if The exact version is 12.2.0, 12.2.1, 12.2.2, 12.2.3, 12.2.4, 12.2.5, 12.2.6, 12.2.7, 12.3.0, 12.3.1, 12.3.2, 12.3.3, 12.3.4, 12.4.0, 12.4.1, 12.4.2, 12.5.0, or any 12.2.x-12.5.0 variant in between
You are affected if your GitLab installation is Enterprise Edition version 12.2.0 or later but earlier than 12.5.1, as this version range contains the improper authorization checks vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 data12.5.1
Upgrade GitLab EE to version 12.5.1 or later which contains the patch for this access control issue. If immediate upgrading is not possible, review user role permissions and restrict access to sensitive features as a temporary measure.
Fix this in GitLab
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19256 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-19256 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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