dbcve.org
GitLabApplication

CVE-2024-6530

MEDIUM · 5.4 CVSS v3.1 Published 2024-10-10
Fix available
A fix is available. Upgrade to 17.2.9 / 17.3.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 17.1 prior 17.2.9, starting from 17.3 prior to 17.3.5, and starting from 17.4 prior to 17.4.2. When adding a authorizing an application, it can be made to render as HTML 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 · moderate confidence

Cross-site scripting (XSS) vulnerability in GitLab's OAuth application authorization flow. An attacker can inject malicious HTML/JavaScript through the application authorization page, which renders under specific circumstances allowing session hijacking or credential theft.

MitigationUpgrade GitLab to version 17.2.9, 17.3.5, or 17.4.2 (or later) to patch the XSS vulnerability in the OAuth application authorization component.

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:>= 17.1.0, < 17.2.9>= 17.3.0, < 17.3.5>= 17.4.0, < 17.4.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. Determine installed GitLab version
    Run `sudo gitlab-rake gitlab:env:info` or check the GitLab admin area under Help > Version to find the exact version number
    Affected if The installed version falls within 17.1.0 to 17.2.8, 17.3.0 to 17.3.4, or 17.4.0 to 17.4.1
  2. Check if OAuth applications exist
    Navigate to GitLab admin area > Applications > OAuth Applications, or use the API endpoint `/api/v4/applications` with admin credentials to list configured OAuth applications
    Affected if Any OAuth applications are registered in the GitLab instance
  3. Verify OAuth authorization flow is accessible
    Attempt to access the OAuth authorization endpoint at `/oauth/authorize` for any registered OAuth application, or check if users can authorize third-party applications
    Affected if Users can reach and interact with the OAuth authorization page
  4. Review application authorization settings
    Check the authorized applications list at `/oauth/authorized_applications` or review which users have authorized OAuth applications in the system
    Affected if There are users who have authorized OAuth applications, making them potential targets for the XSS

A GitLab instance is affected if it runs version 17.1.0 through 17.2.8, 17.3.0 through 17.3.4, or 17.4.0 through 17.4.1 AND has OAuth applications that users can authorize.

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.2.9 / 17.3.5 / 17.4.2 or later
Fixed in 17.2.917.3.517.4.2
Interim mitigation

Upgrade GitLab to version 17.2.9, 17.3.5, or 17.4.2 (or later) to patch the XSS vulnerability in the OAuth application authorization component.

Recommended fix High confidence

Upgrade to GitLab 17.4.2 (or the latest 17.4.x stable), or 17.3.5, or 17.2.9 depending on your release line

  1. 1. Back up your GitLab instance data and configuration before proceeding with the upgrade.
  2. 2. Identify your current GitLab version by navigating to Admin Area > Settings > General or running `sudo gitlab-rake gitlab:env:info`.
  3. 3. If running 17.1.x: upgrade to version 17.2.9 or later; if running 17.3.x: upgrade to version 17.3.5 or later; if running 17.4.0-17.4.1: upgrade to version 17.4.2 or later.
  4. 4. For self-managed GitLab, follow the official upgrade documentation for your installation method (package manager, Docker, source).
  5. 5. After upgrade, verify the new version is running: `sudo gitlab-rake gitlab:env:info`.
  6. 6. Test that the OAuth application authorization flow renders correctly and does not execute malicious scripts.
Caveat Standard GitLab upgrade risks apply - review release notes for any required migrations or configuration changes between your current and target version

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

Fix this in GitLab Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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