dbcve.org
GitLabApplication

CVE-2023-0155

MEDIUM · 5.4 CVSS v3.1 Published 2023-05-03
Fix available
A fix is available. Upgrade to 15.8.5 / 15.9.5 or later.
See remediation →
58/100
Remediation priority · Elevated
Public exploit Remotely reachable

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 CE/EE affecting all versions before 15.8.5, 15.9.4, 15.10.1. Open redirects was possible due to framing arbitrary content on any page allowing user controlled markdown

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
How this class of weakness works · CWE-601

The application redirects the browser to a URL taken from user input without validating it, so an attacker can craft a link on your trusted domain that quietly bounces victims to a malicious site. It is a staple of phishing and token theft. The fix is to allow-list redirect destinations or use indirect reference keys, never a raw user-supplied URL.

General guidance for the open redirect class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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:< 15.8.5>= 15.9, < 15.9.5>= 15.10, < 15.10.1

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
Low
User interaction
Required
Scope
Changed
Confidentiality
None
Integrity
Low
Availability
Low

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

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 15.8.5 / 15.9.5 / 15.10.1 or later
Fixed in 15.8.515.9.515.10.1
Recommended fix High confidence

Upgrade to GitLab 15.8.5, 15.9.5, 15.10.1, or later (preferably the latest stable 15.x release)

  1. 1. Identify the current GitLab version by navigating to the GitLab admin area or running `gitlab-rake gitlab:env:info`
  2. 2. Determine the appropriate upgrade path based on current version: if < 15.8.5 upgrade to 15.8.5; if 15.9.0-15.9.4 upgrade to 15.9.5; if 15.10.0 upgrade to 15.10.1 or later
  3. 3. Create a full backup of the GitLab instance using `gitlab-backup create`
  4. 4. Stop GitLab services with `gitlab-ctl stop`
  5. 5. Update GitLab using the official package manager for your installation (omnibus) or by following the upgrade guide for installations from source
  6. 6. Run `gitlab-ctl reconfigure` after package installation
  7. 7. Start GitLab services with `gitlab-ctl start`
  8. 8. Verify the upgrade was successful and the vulnerability is fixed by checking the GitLab version and testing that markdown rendering no longer allows arbitrary framing
Caveat Standard GitLab minor version upgrades typically have minimal breaking changes; review the release notes for any known issues before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $900. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-0155 — 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-0155 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