GitLabApplication
CVE-2019-19261
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) 6.7 and later through 12.5 allows SSRF.
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 confidenceServer-Side Request Forgery (SSRF) vulnerability in GitLab Enterprise Edition allowing remote attackers to make the server perform requests to arbitrary internal or external resources. Affects versions 6.7 through 12.5.
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
>= 6.7.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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify GitLab installation type and versionRun `gitlab-rake gitlab:env:info` or check the Admin Area dashboard under the Help section to see the exact version number installedAffected if The displayed version falls within 6.7.0 to 12.5.0 inclusive, meaning it is before the 12.5.1 security patch
-
Confirm GitLab edition is Enterprise EditionCheck the Admin Area under Overview > Dashboard or run `gitlab-ee --version` if available; the vulnerability specifically affects Enterprise Edition (EE)Affected if The installation is GitLab Enterprise Edition (EE) and the version is in the affected range
-
Verify network accessibility of the GitLab instanceDetermine if the GitLab web interface is reachable from untrusted networks (public internet or guest VLANs) by reviewing firewall rules, load balancer configuration, or network ACLsAffected if The GitLab instance is exposed to untrusted networks and runs a vulnerable version, allowing attackers to trigger the SSRF via web requests
-
Audit outbound network restrictionsReview security groups, firewall policies, or network segmentation rules controlling what destinations the GitLab server can initiate connections toAffected if The GitLab server has unrestricted outbound access to internal resources and runs a vulnerable version
A user is affected if their GitLab installation is Enterprise Edition version 6.7.0 through 12.5.0 and is network-accessible to untrusted parties, allowing them to trigger malicious request generation.
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.6 or later which contains the security patch. For systems that cannot be immediately upgraded, implement network segmentation and restrict outbound access from the GitLab server.
Fix this in GitLab
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19261 — 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-19261 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