GitLabApplication
CVE-2022-3280
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 in GitLab CE/EE affecting all versions from 10.1 prior to 15.3.5, 15.4 prior to 15.4.4, and 15.5 prior to 15.5.2 allows an attacker to trick users into visiting a trustworthy URL and being redirected to arbitrary content.
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 in GitLab CE/EE allows attackers to craft malicious URLs that appear to be on a trustworthy GitLab domain but actually redirect users to arbitrary external websites, enabling phishing attacks.
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.1.0, < 15.3.5>= 15.4.0, < 15.4.4>= 15.5.0, < 15.5.2CVSS 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 installed GitLab versionRun command: gitlab-rake gitlab:env:info or check /opt/gitlab/embedded/service/gitlab-rails/VERSION file. Alternatively, go to Admin Area > Settings > General and view the GitLab version displayed.Affected if Version falls within >= 10.1.0 AND < 15.3.5, OR >= 15.4.0 AND < 15.4.4, OR >= 15.5.0 AND < 15.5.2
-
Identify if user-facing redirect functionality existsReview application configuration files in /etc/gitlab/gitlab.rb for redirect-related settings. Check for any URL forwarding or redirect features enabled in the GitLab Rails application.Affected if Redirect functionality is enabled and accessible to unauthenticated or low-privileged users
-
Test for open redirect vulnerabilityAttempt to access a known GitLab endpoint with a crafted redirect parameter pointing to an external domain, such as /users/sign_in?redirect=//attacker.com. Observe whether the application permits the redirect.Affected if The application redirects to an arbitrary external domain without validation
The environment is affected if the installed GitLab version matches any of the three vulnerable ranges AND the redirect functionality is accessible to attackers.
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 · scoped15.3.515.4.415.5.2
Upgrade GitLab to version 15.3.5, 15.4.4, 15.5.2 or later. Alternatively, implement URL validation to reject redirects to untrusted domains.
Upgrade to GitLab 15.3.5, 15.4.4, or 15.5.2 (or later stable release)
- 1. Backup your GitLab instance data and configuration before proceeding with the upgrade
- 2. Review the GitLab upgrade documentation for your current version at https://docs.gitlab.com/ee/update/
- 3. Plan your upgrade path based on your current version: if on 10.1.0 to 15.2.x, upgrade to 15.3.5 or later; if on 15.4.0 to 15.4.3, upgrade to 15.4.4 or later; if on 15.5.0 to 15.5.1, upgrade to 15.5.2 or later
- 4. For self-managed installations, update your package repository and run the appropriate upgrade command for your installation method
- 5. Verify the upgrade was successful by logging into GitLab
- 6. Test that the open redirect vulnerability is no longer present by attempting to use a redirect parameter with an external domain
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
- Testing4.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 $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3280 — 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-3280 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