GitLabApplication
CVE-2019-18451
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 10.7.4 through 12.4 in the InternalRedirect filtering feature. It has an Open Redirect.
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 confidenceAn Open Redirect vulnerability exists in GitLab Community and Enterprise Edition versions 10.7.4 through 12.4 within the InternalRedirect feature. The filtering mechanism for internal redirects is insufficient, allowing attackers to craft malicious URLs that appear to be on the trusted GitLab domain but actually redirect users to external malicious sites.
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
>= 10.7.4, <= 12.4.0CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 your GitLab versionRun the command 'gitlab-rake gitlab:env:info' or check the version file typically located at /opt/gitlab/version to obtain the installed GitLab version numberAffected if The installed version is 10.7.4, 10.8.x, 11.x, 12.0, 12.1, 12.2, 12.3, or 12.4.0 (any version from 10.7.4 through 12.4.0 inclusive)
-
Confirm the InternalRedirect feature is accessibleIdentify if your GitLab instance exposes the internal redirect endpoint. This typically involves URLs matching the pattern /-/internal_redirect?target=... which may appear in logs or be accessible via web requestsAffected if The InternalRedirect feature is enabled and accessible on your GitLab instance, and the version falls within the affected range
-
Review redirect URL validationExamine your GitLab configuration files (typically in /etc/gitlab/gitlab.rb or within the Rails application) for any custom redirect validation rules that may mitigate external URL redirectionAffected if There is NO custom URL validation configured to restrict redirect targets to internal domains only, and the version is within the affected range
You are affected if your GitLab version is 10.7.4 through 12.4.0 and the InternalRedirect feature is accessible without additional validation preventing external redirects
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 dataUpdate GitLab to a version newer than 12.4 where the vulnerability has been patched. If immediate patching is not possible, implement URL validation to ensure redirect targets remain within the expected domain and reject external URLs.
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-18451 — 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-18451 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