GitLabApplication
CVE-2022-2250
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 open redirect vulnerability in GitLab EE/CE affecting all versions from 11.1 prior to 14.10.5, 15.0 prior to 15.0.4, and 15.1 prior to 15.1.1, allows an attacker to redirect users to an arbitrary location if they trust the URL.
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 confidenceOpen redirect vulnerability in GitLab EE/CE allows attackers to craft malicious URLs that appear trusted but redirect users to arbitrary external sites. The application fails to properly validate redirect targets before forwarding users.
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
>= 11.1.0, < 14.0.5>= 11.1.0, < 14.10.5>= 15.0.0, < 15.0.4= 15.1.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.
-
Identify installed GitLab versionRun `cat /opt/gitlab/version` for Omnibus installations, or `gitlab-rake gitlab:env:info` to display version details, or access the Admin Dashboard and navigate to Help > Version to view the running versionAffected if The version displayed falls within any of these ranges: 11.1.0 to 14.0.4, 14.1.0 to 14.10.4, 15.0.0 to 15.0.3, or exactly 15.1.0
-
Confirm version via API (alternative method)Query the GitLab API endpoint `/api/v4/version` using curl or similar tool to retrieve the version string programmaticallyAffected if The returned version matches the affected ranges listed in step 1
-
Verify redirect handling if on affected versionInspect application logs or test redirect behavior by observing URL parameters in requests; the vulnerability exists in the redirect validation logic itself rather than a specific configuration settingAffected if Running an affected version means the open redirect flaw is present in the codebase regardless of configuration
A user is affected if their installed GitLab version falls within 11.1.0 to 14.0.4, 14.1.0 to 14.10.4, 15.0.0 to 15.0.3, or exactly 15.1.0, as these versions contain the unvalidated redirect 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.
dbcve · scoped14.0.514.10.515.0.4
Upgrade GitLab to version 14.10.5, 15.0.4, 15.1.1 or later to patch the open redirect vulnerability.
14.10.5 (or later 14.x), 15.0.4 (or later 15.0.x), or 15.1.1 (or later 15.1.x)
- Identify your current GitLab version using the Rails console (`gitlab-rake gitlab:env:info`) or the admin area
- Determine which version branch you are on (14.x, 15.0.x, or 15.1.x)
- For GitLab 14.x: Upgrade to version 14.10.5 or later (14.10.5, 14.11.x, 14.12.x, etc.)
- For GitLab 15.0.x: Upgrade to version 15.0.4 or later
- For GitLab 15.1.0: Upgrade to version 15.1.1 or later
- After upgrade, verify the fix by testing redirect functionality in GitLab
- Review the GitLab release notes for your target version for any known issues
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in GitLab
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2250 — 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-2022-2250 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