dbcve.org
GitLabApplication

CVE-2023-1836

MEDIUM · 5.4 CVSS v3.1 Published 2023-05-03
Fix available
A fix is available. Upgrade to 15.9.6 / 15.10.5 or later.
See remediation →
58/100
Remediation priority · Elevated
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
A cross-site scripting issue has been discovered in GitLab affecting all versions starting from 5.1 before 15.9.6, all versions starting from 15.10 before 15.10.5, all versions starting from 15.11 before 15.11.1. When viewing an XML file in a repository in "raw" mode, it can be made to render as HTML if viewed under specific circumstances

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 confidence

GitLab contains a cross-site scripting vulnerability where XML files viewed in raw mode can be rendered as HTML under specific circumstances, allowing injection of malicious scripts.

MitigationUpgrade GitLab to version 15.9.6, 15.10.5, or 15.11.1 or later. Alternatively, restrict or disable raw file viewing for XML content until patched.

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:>= 5.1, < 15.9.6>= 15.10, < 15.10.5>= 15.11, < 15.11.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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Determine installed GitLab version
    Run command: gitlab-rake gitlab:env:info or check /opt/gitlab/version, or look at the GitLab admin dashboard under 'Help' > 'Version'
    Affected if Version falls within ranges: >=5.1 and <15.9.6, OR >=15.10 and <15.10.5, OR >=15.11 and <15.11.1
  2. Verify raw file viewing is accessible
    Confirm that the GitLab instance allows users to view raw file content. This is enabled by default in standard GitLab installations. Check via admin settings under 'Settings' > 'Repository' > 'Raw blobs' setting
    Affected if Raw file viewing is enabled and accessible to users
  3. Check for XML file storage
    Identify if any XML files exist in repositories hosted on this GitLab instance. Browse repositories or search for .xml file extensions
    Affected if XML files are stored in any accessible repository on the instance
  4. Confirm raw view rendering behavior
    Access an XML file in a repository via the raw view (click 'Open' then 'raw' button on an XML file, or navigate to /-/raw/master/path/to/file.xml)
    Affected if The XML content renders or executes rather than downloads as plain text, indicating the XSS condition exists

Your environment is affected if the installed GitLab version is within the vulnerable ranges AND raw file viewing for XML content is enabled and accessible to users.

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 15.9.6 / 15.10.5 / 15.11.1 or later
Fixed in 15.9.615.10.515.11.1
Interim mitigation

Upgrade GitLab to version 15.9.6, 15.10.5, or 15.11.1 or later. Alternatively, restrict or disable raw file viewing for XML content until patched.

Recommended fix High confidence

15.11.1 or later (or at minimum 15.9.6/15.10.5 depending on your current branch)

  1. Identify your current GitLab version using the GitLab admin area or `gitlab-rake gitlab:env:info`
  2. Consult the official GitLab upgrade guide for your current version: https://docs.gitlab.com/ee/update/
  3. Plan your upgrade path - if upgrading across multiple minor versions, upgrade through each intermediate version sequentially
  4. Back up your GitLab database and repositories before upgrading
  5. Upgrade to GitLab 15.9.6 or later (if currently on 15.9.x), 15.10.5 or later (if currently on 15.10.x), or 15.11.1 or later (if currently on 15.11.x)
  6. After upgrade, verify the XML raw view functionality works correctly
Caveat Point releases typically have minimal breaking changes, but review release notes for any configuration or database migration requirements

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
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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