GitLabApplication
CVE-2024-4901
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 · uneditedAn issue was discovered in GitLab CE/EE affecting all versions starting from 16.9 prior to 16.11.5, starting from 17.0 prior to 17.0.3, and starting from 17.1 prior to 17.1.1, where a stored XSS vulnerability could be imported from a project with malicious commit notes.
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 confidenceA stored XSS vulnerability exists in GitLab CE/EE where malicious commit notes containing XSS payloads can be imported from one project into another. When users view the imported commit notes, the embedded JavaScript executes in their browser context.
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
>= 16.9.0, < 16.11.5>= 17.0.0, < 17.0.3= 17.1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed GitLab versionRun `gitlab-rake gitlab:env:info` or check the GitLab admin area under /admin/application_settings to find the exact version numberAffected if The version falls within 16.9.0 to 16.11.4, 17.0.0 to 17.0.2, or equals 17.1.0
-
Verify if project import functionality is accessibleCheck whether any users have permissions to import projects or merge requests between projects, as this feature is required for the attack vectorAffected if Project import or merge request import features are enabled and accessible to users
-
Inspect for imported commit notes in repositoriesReview project repositories for commit notes that were imported from external or untrusted sources using the import featureAffected if Any commit notes exist that were imported from projects outside your trusted internal environment
-
Search commit note content for suspicious patternsQuery the database or use GitLab search to examine commit note content for XSS indicators such as script tags, javascript: URIs, or event handler attributesAffected if Any commit notes contain JavaScript code, HTML script tags, or encoded XSS payloads in their content
A user is affected if their GitLab version is within the affected ranges AND any imported commit notes from untrusted sources exist in the environment.
Generated from the published advisory. Verify against your own configuration.
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 · scoped16.11.517.0.3
Upgrade GitLab to version 16.11.5, 17.0.3, or 17.1.1 or later. Audit projects for any imported commit notes from untrusted sources prior to patching.
16.11.5, 17.0.3, or 17.1.1+ (depending on your release line)
- Identify your current GitLab version using the GitLab Rails console or admin area
- Upgrade GitLab to version 16.11.5 or later if using the 16.x line
- Alternatively, upgrade to version 17.0.3 or later if using the 17.0.x line
- Alternatively, upgrade to version 17.1.1 or later if using the 17.1.x line
- After upgrade, verify the version in the admin dashboard to confirm the patch was applied
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 / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-4901 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-4901 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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