dbcve.org
GitLabApplication

CVE-2024-5528

MEDIUM · 5.4 CVSS v3.1 Published 2025-02-05
Fix available
A fix is available. Upgrade to 16.11.6 / 17.0.4 or later.
See remediation →
60/100
Remediation priority · Elevated
Public exploit Remotely reachable Zero-click

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
An issue was discovered in GitLab CE/EE affecting all versions prior to 16.11.6, starting from 17.0 prior to 17.0.4, and starting from 17.1 prior to 17.1.2, which allows a subdomain takeover in GitLab Pages.

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

A detailed technical summary for this CVE is being prepared.

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:< 16.11.6>= 17.0.0, < 17.0.4>= 17.1.0, < 17.1.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
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

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 16.11.6 / 17.0.4 / 17.1.2 or later
Fixed in 16.11.617.0.417.1.2
Recommended fix High confidence

16.11.6, 17.0.4, or 17.1.2 (depending on your current version branch)

  1. Identify your current GitLab version by checking the GitLab administration panel or running `gitlab-rake gitlab:env:info`
  2. Determine which version branch you are currently on (16.x, 17.0.x, or 17.1.x)
  3. Plan your upgrade path based on your current version - for versions below 16.11.6, upgrade to 16.11.6; for versions 17.0.x below 17.0.4, upgrade to 17.0.4; for versions 17.1.x below 17.1.2, upgrade to 17.1.2
  4. Backup your GitLab data and database before performing the upgrade
  5. Follow the official GitLab upgrade documentation for your installation method (omnibus, source, or docker)
  6. After upgrade, verify GitLab Pages is functioning correctly and the subdomain takeover vulnerability is resolved
  7. Review GitLab Pages configuration to ensure proper domain validation is in place
Caveat Standard GitLab patch upgrades typically have minimal breaking changes; always review release notes for deprecation warnings before upgrading

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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