GitLabApplication
CVE-2024-9633
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 has been discovered in GitLab CE/EE affecting all versions starting from 16.3 before 17.4.2, all versions starting from 17.5 before 17.5.4, all versions starting from 17.6 before 17.6.2. This issue allows an attacker to create a group with a name matching an existing unique Pages domain, potentially leading to domain confusion attacks.
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 confidenceThis GitLab vulnerability allows attackers to create a group with a name that matches an existing unique Pages domain. GitLab Pages assigns unique domains to hosted static sites, and this flaw permits name collisions that could enable domain confusion attacks for phishing or impersonation of legitimate Pages-hosted sites.
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.3.0, < 17.4.2>= 17.5.0, < 17.5.4>= 17.6.0, < 17.6.2CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
-
Check installed GitLab versionRun `sudo gitlab-rake gitlab:env:info` or check the admin area dashboard for the exact version numberAffected if The version is >= 16.3.0 and < 17.4.2, OR >= 17.5.0 and < 17.5.4, OR >= 17.6.0 and < 17.6.2
-
Verify GitLab Pages is enabledNavigate to Admin Area > Settings > Pages or run `sudo gitlab-ctl status | grep -i pages`. Also check the gitlab.yml configuration file for pages enabled statusAffected if GitLab Pages feature is enabled on the instance
-
Enumerate existing Pages domainsQuery the database: `sudo gitlab-rails dbconsole -e "SELECT domain, project_id FROM pages_domains;"` or check the Admin Area > Pages for a list of deployed static sites and their domainsAffected if There are active Pages domains configured on the instance
-
Audit recent group creation for domain name collisionsQuery recent groups: `sudo gitlab-rails dbconsole -e "SELECT name, path, created_at FROM namespaces WHERE created_at > NOW() - INTERVAL '30 days' ORDER BY created_at DESC;"` and compare against the Pages domains list from step 3Affected if Any recently created group name exactly matches an existing Pages domain name
You are affected if your GitLab version falls within the vulnerable ranges AND GitLab Pages is enabled AND an attacker was able to create a group with a name matching an existing Pages domain.
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 · scoped17.4.217.5.417.6.2
Upgrade GitLab to version 17.4.2, 17.5.4, or 17.6.2 or later. As a compensating control, monitor for suspicious group creation requests matching existing Pages domain names.
17.6.2 or later (recommended: latest 17.x stable release)
- 1. Back up your GitLab instance database and repository data before upgrading
- 2. Consult the GitLab upgrade documentation for your current version
- 3. Plan your upgrade path - you need to reach at least one of these fixed versions: 17.4.2, 17.5.4, or 17.6.2
- 4. For versions 16.3.x through 17.3.x: upgrade directly to 17.4.2 or later
- 5. For version 17.4.x: upgrade to 17.4.2 or later
- 6. For version 17.5.x: upgrade to 17.5.4 or later
- 7. For version 17.6.0-17.6.1: upgrade to 17.6.2
- 8. After upgrade, verify group creation cannot use existing unique Pages domain names
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
- 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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9633 — 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-9633 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