GitLabApplication
CVE-2019-15730
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 · uneditedAn issue was discovered in GitLab Community and Enterprise Edition 8.14 through 12.2.1. The Jira integration contains a SSRF vulnerability as a result of a bypass of the current protection mechanisms against this type of attack, which would allow sending requests to any resources accessible in the local network by the GitLab server.
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 confidenceGitLab's Jira integration contains an SSRF vulnerability allowing attackers to bypass existing protections and send requests from the GitLab server to internal network resources. The flaw enables enumeration and potential exploitation of services accessible only from the GitLab server's perspective, such as internal APIs, databases, or administrative interfaces.
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
>= 8.14.0, < 12.0.8>= 12.1.0, < 12.1.8>= 12.2.0, < 12.2.3CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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.
-
Determine installed GitLab versionRun 'gitlab-rake gitlab:env:info' or check the GitLab admin panel at /admin/application_settings to view the version numberAffected if The version falls within any of these ranges: >= 8.14.0 and < 12.0.8; >= 12.1.0 and < 12.1.8; or >= 12.2.0 and < 12.2.3
-
Identify if Jira integration is configuredNavigate to GitLab Admin Area > Applications or check project-level integration settings to see if a Jira integration link existsAffected if Jira integration is enabled or configured in any project or at the instance level
-
Locate GitLab configuration filesCheck /etc/gitlab/gitlab.rb or /var/opt/gitlab/gitlab-rails/etc/gitlab.yml for Jira-related settings under the 'integrations' or 'jira' sectionAffected if Jira integration settings are present and the GitLab version is vulnerable
-
Verify network access from GitLab serverReview network logs or firewall rules to determine if the GitLab server has been making outbound requests to unexpected internal IP rangesAffected if Unexpected internal network requests have originated from the GitLab server to ports or addresses associated with internal services
You are affected if your GitLab version is one of the vulnerable versions listed AND the Jira integration is configured or enabled, as the SSRF flaw only triggers through this integration feature.
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.0.812.1.812.2.3
Upgrade GitLab to version 12.2.2 or later. If immediate patching is not possible, restrict network access to the GitLab server and review/disable the Jira integration until the patch can be applied.
Fix this in GitLab
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15730 — 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-15730 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