dbcve.org
GitLabApplication

CVE-2024-4207

MEDIUM · 5.4 CVSS v3.1 Published 2024-08-08
Fix available
A fix is available. Upgrade to 17.0.6 / 17.1.4 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 prior 17.0.6, starting from 17.1 prior to 17.1.4, and starting from 17.2 prior to 17.2.2. 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

A stored cross-site scripting (XSS) vulnerability in GitLab allows attackers to embed malicious XML content that renders as HTML when viewed in raw mode under specific circumstances. This enables script execution in the context of other users viewing the file.

MitigationUpgrade GitLab to version 17.0.6, 17.1.4, 17.2.2 or later. Until then, avoid viewing untrusted XML files in raw mode and disable raw file rendering for XML MIME types if possible.

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.0, < 17.0.6>= 17.1.0, < 17.1.4>= 17.2.0, < 17.2.2

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. Check installed GitLab version
    Run `sudo gitlab-rake gitlab:env:info` or check the GitLab admin panel under Help > Version to find the exact version number
    Affected if The installed version falls within: >= 5.1.0 and < 17.0.6; OR >= 17.1.0 and < 17.1.4; OR >= 17.2.0 and < 17.2.2
  2. Verify raw file viewing is accessible
    Attempt to access any stored file via the raw endpoint by appending `/raw` to the file URL (e.g., `https://your-gitlab-instance/project/-/blob/main/file.xml/raw`)
    Affected if Raw file viewing is enabled and users can view XML files in raw mode (this is enabled by default in GitLab)
  3. Identify XML file repositories
    Search project repositories for `.xml` files using the GitLab UI (Projects > Repository > Files) or via API: `GET /projects/:id/repository/tree?path=&format=xml`
    Affected if XML files exist in accessible repositories that users can view in raw mode

You are affected if you run a vulnerable GitLab version (listed in step 1) AND have XML files that users can view in raw mode on your instance.

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 17.0.6 / 17.1.4 / 17.2.2 or later
Fixed in 17.0.617.1.417.2.2
Interim mitigation

Upgrade GitLab to version 17.0.6, 17.1.4, 17.2.2 or later. Until then, avoid viewing untrusted XML files in raw mode and disable raw file rendering for XML MIME types if possible.

Recommended fix High confidence

Upgrade to GitLab 17.2.2 or later (preferably latest 17.x stable release)

  1. 1. Back up your GitLab instance database and repository data
  2. 2. Schedule a maintenance window as upgrade may require downtime
  3. 3. For Omnibus installations: Run 'sudo gitlab-rake gitlab:backup:create' to create a full backup
  4. 4. For Omnibus: Update package repository and install: 'sudo apt-get update' then 'sudo apt-get install gitlab-ce' or 'sudo apt-get install gitlab-ee'
  5. 5. For source installations: Stop GitLab, download the fixed version (17.2.2 or later), and follow upgrade instructions in doc/upgrade.md
  6. 6. After installation, run 'sudo gitlab-ctl reconfigure'
  7. 7. Verify the upgrade by checking GitLab version at /admin/about
  8. 8. Test XML file viewing in raw mode to confirm the vulnerability is fixed
Caveat Minor version upgrades within 17.x are generally safe with no breaking changes; ensure you review GitLab release notes for any specific caveats

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-2024-4207 — 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-2024-4207 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