dbcve.org
GitLabApplication

CVE-2024-4472

MEDIUM · 5.5 CVSS v3.1 Published 2024-09-12
Fix available
A fix is available. Upgrade to 17.1.7 / 17.2.5 or later.
See remediation →
57/100
Remediation priority · Elevated
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 starting from 16.5 prior to 17.1.7, starting from 17.2 prior to 17.2.5, and starting from 17.3 prior to 17.3.2, where dependency proxy credentials are retained in graphql Logs.

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

GitLab CE/EE versions 16.5 through 17.3.1 contained a vulnerability where dependency proxy credentials were inadvertently being written to GraphQL logs, exposing sensitive authentication credentials to anyone with log access.

MitigationUpgrade to GitLab 17.1.7, 17.2.5, or 17.3.2 or later. Additionally, audit GraphQL logs for exposed credentials and rotate any potentially compromised credentials as a precautionary measure.

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:>= 16.5.0, < 17.1.7>= 17.2.0, < 17.2.5>= 17.3.0, < 17.3.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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 Admin Area > Overview > System Info in the web UI to view the GitLab version number
    Affected if The installed version falls within any of these ranges: 16.5.0 to 17.1.6, 17.2.0 to 17.2.4, or 17.3.0 to 17.3.1
  2. Verify dependency proxy is in use
    Check if any projects or groups have the dependency proxy feature enabled by navigating to the project or group Settings > Packages and registries > Dependency proxy, or run `sudo gitlab-rails console` and query for projects with dependency proxy enabled
    Affected if Dependency proxy is enabled for any project or group in the GitLab instance
  3. Inspect GraphQL logs for credential leakage
    Locate GraphQL log files typically found in /var/log/gitlab/gitlab-rails/graphql_json.log or /var/log/gitlab/gitlab-rails/production.log, then search for strings like 'dependency_proxy' or 'credentials' using grep or a log analysis tool
    Affected if Log entries contain dependency proxy credentials, authentication tokens, or password-like strings in GraphQL query contexts

A user is affected if they are running a vulnerable GitLab version (16.5.0-17.1.6, 17.2.0-17.2.4, or 17.3.0-17.3.1), have the dependency proxy feature enabled, and have not audited their GraphQL logs for exposed credentials.

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.1.7 / 17.2.5 / 17.3.2 or later
Fixed in 17.1.717.2.517.3.2
Interim mitigation

Upgrade to GitLab 17.1.7, 17.2.5, or 17.3.2 or later. Additionally, audit GraphQL logs for exposed credentials and rotate any potentially compromised credentials as a precautionary measure.

Recommended fix High confidence

Upgrade to GitLab 17.3.2 or later (17.2.5+ or 17.1.7+ are also fixed)

  1. 1. Back up your GitLab instance database and repositories before starting the upgrade.
  2. 2. Ensure you are currently running one of the affected versions: 16.5.0 through 17.1.6, 17.2.0 through 17.2.4, or 17.3.0 through 17.3.1.
  3. 3. Plan for downtime as GitLab upgrade requires stopping services.
  4. 4. Update your GitLab package repository to the latest available repository.
  5. 5. For GitLab installations using the Omnibus package, run: sudo apt-get update && sudo apt-get install gitlab-ce (or gitlab-ee for Enterprise Edition).
  6. 6. Alternatively, for Docker installations, pull the fixed version: docker pull gitlab/gitlab-ee:17.3.2 or a later stable release.
  7. 7. After installation, reconfigure GitLab: sudo gitlab-ctl reconfigure.
  8. 8. Verify the upgrade was successful by checking the GitLab version at /admin/about.
Caveat Standard GitLab upgrade considerations apply - review release notes for any between-version migrations or configuration changes

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-4472 — 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-4472 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