dbcve.org
GitLabApplication

CVE-2024-7554

MEDIUM · 6.5 CVSS v3.1 Published 2024-08-08
Fix available
A fix is available. Upgrade to 17.0.6 / 17.1.4 or later.
See remediation →
71/100
Remediation priority · Elevated
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 has been discovered in GitLab CE/EE affecting all versions starting from 13.9 before 17.0.6, all versions starting from 17.1 before 17.1.4, all versions starting from 17.2 before 17.2.2. Under certain conditions, access tokens may have been logged when an API request was made in a specific manner.

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 confidence

In affected GitLab CE/EE versions (13.9 through 17.2.1), access tokens can be inadvertently written to application logs when API requests are made using a specific request method or pattern. This exposes sensitive authentication credentials through log files.

MitigationUpgrade GitLab to version 17.0.6, 17.1.4, or 17.2.2 or later. Review existing application logs for exposed tokens and rotate any credentials that may have been logged.

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:>= 13.9, < 17.0.6>= 17.1.0, < 17.1.4>= 17.2.0, < 17.2.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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/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. Determine installed GitLab version
    Run `gitlab-rake gitlab:env:info` or check `/opt/gitlab/version` to obtain the exact version number
    Affected if The version falls within 13.9 to 17.0.5, 17.1.0 to 17.1.3, or 17.2.0 to 17.2.1
  2. Verify API access tokens are in use
    Check if any API access tokens (personal access tokens or OAuth tokens) have been created and used in the GitLab instance by reviewing user accounts and API integration configurations
    Affected if API access tokens exist and have been used for authentication
  3. Inspect application logs for token leakage
    Search GitLab production logs (typically in `/var/log/gitlab/gitlab-rails/production.log` or via `gitlab-ctl tail gitlab-rails`) for patterns matching bearer tokens or "token" strings alongside API request records
    Affected if Log files contain raw access token strings in API request entries
  4. Check for the specific request pattern
    Review API request logs for the particular HTTP method or request pattern that triggers the logging behavior (examine requests to /api/v4 endpoints)
    Affected if API requests using the vulnerable pattern have been logged with credentials visible in plain text

You are affected if your GitLab version is within the vulnerable ranges AND API access tokens have been used, resulting in credentials appearing in application log files.

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.0.6 / 17.1.4 / 17.2.2 or later
Fixed in 17.0.617.1.417.2.2
Interim mitigation

Upgrade GitLab to version 17.0.6, 17.1.4, or 17.2.2 or later. Review existing application logs for exposed tokens and rotate any credentials that may have been logged.

Recommended fix High confidence

17.2.2 (or later 17.x stable release)

  1. Identify current GitLab version using GitLab administration interface or `gitlab-rake gitlab:env:info`
  2. Plan upgrade path based on current version - aim for latest stable release in your major version line
  3. Back up GitLab database and repositories before upgrading
  4. For Omnibus installations: run `sudo gitlab-ctl stop` then `sudo apt-get update && sudo apt-get install gitlab-ce` (or gitlab-ee)
  5. For source installations: follow upgrade documentation for your installation method
  6. After upgrade, verify GitLab is running with `sudo gitlab-ctl status`
  7. Review GitLab logs to confirm access tokens are no longer being logged (check /var/log/gitlab/gitlab-rails/production.log)
Caveat Major version upgrades from 13.x/14.x/15.x to 16.x/17.x may require additional migration steps and have breaking changes - review GitLab upgrade guides

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
14.0 hours of engineering $2,490
Get the upgrade done

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 locally
dbcve dependency scanner

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