dbcve.org
GitLabApplication

CVE-2023-3922

HIGH · 7.1 CVSS v3.1 Published 2023-09-29
Fix available
A fix is available. Upgrade to 16.2.8 / 16.3.5 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
An issue has been discovered in GitLab affecting all versions starting from 8.15 before 16.2.8, all versions starting from 16.3 before 16.3.5, all versions starting from 16.4 before 16.4.1. It was possible to hijack some links and buttons on the GitLab UI to a malicious page.

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 confidence

GitLab versions 8.15 through 16.2.7, 16.3.0 through 16.3.4, and 16.4.0 contain a vulnerability allowing attackers to hijack certain links and buttons in the GitLab UI, redirecting users to malicious external pages. This is likely an open redirect or UI manipulation flaw in how the application handles link generation and button destinations.

MitigationUpgrade GitLab to version 16.2.8, 16.3.5, 16.4.1, or later. For self-hosted deployments, apply the appropriate patch version; for GitLab.com, no action is required as the service is managed by GitLab.

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
Affected:>= 8.15, < 16.2.8>= 16.3.0, < 16.3.5= 16.4.0

CVSS 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
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify GitLab installation
    Locate GitLab installation directories (common paths: /opt/gitlab, /var/opt/gitlab) or check if gitlab-ctl command is available on the system
    Affected if GitLab is not installed on the system
  2. Determine installed GitLab version via command line
    Run 'gitlab-rake gitlab:env:info' or 'gitlab-ctl version' if you have CLI access to the GitLab server
    Affected if The displayed version falls within 8.15 to 16.2.7, 16.3.0 to 16.3.4, or equals 16.4.0
  3. Check version via web interface
    Access GitLab web UI and navigate to Help > Version or check the footer of any page for the version number
    Affected if The version shown matches the affected ranges listed above
  4. Inspect version file on disk
    Read /opt/gitlab/VERSION or /var/opt/gitlab/gitlab-rails/VERSION file if present on the filesystem
    Affected if The version string in these files is one of the affected versions

The environment is affected if a self-hosted GitLab instance is running and its installed version matches any of these ranges: 8.15 to 16.2.7, 16.3.0 to 16.3.4, or exactly 16.4.0

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 16.2.8 / 16.3.5 or later
Fixed in 16.2.816.3.5
Interim mitigation

Upgrade GitLab to version 16.2.8, 16.3.5, 16.4.1, or later. For self-hosted deployments, apply the appropriate patch version; for GitLab.com, no action is required as the service is managed by GitLab.

Recommended fix High confidence

16.2.8, 16.3.5, or 16.4.1 (or later stable release within your major version branch)

  1. 1. Identify the current GitLab version by running `gitlab-rake gitlab:env:info` or checking the GitLab admin area
  2. 2. Review the GitLab upgrade documentation at https://docs.gitlab.com/ee/update/
  3. 3. Create a full backup of the GitLab instance using `gitlab-backup-create`
  4. 4. Schedule a maintenance window for the upgrade
  5. 5. Upgrade GitLab to version 16.2.8 or later (if on 16.2.x), 16.3.5 or later (if on 16.3.x), or 16.4.1 or later (if on 16.4.x)
  6. 6. Verify the upgrade was successful and test that the application functions correctly
  7. 7. Confirm the version by checking `gitlab-rake gitlab:env:info`
Caveat Minor version upgrades within the same major release typically have minimal breaking changes, but always review the GitLab release notes for deprecations and required migrations

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
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-3922 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-3922 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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