dbcve.org
GitLabApplication

CVE-2024-5435

MEDIUM · 6.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 →
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 discovered in GitLab EE/CE affecting all versions starting from 15.10 before 17.1.7, all versions starting from 17.2 before 17.2.5, all versions starting from 17.3 before 17.3.2 will disclose user password from repository mirror configuration.

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

GitLab EE/CE versions 15.10 through 17.3.1 contain an information disclosure vulnerability where user passwords stored in repository mirror configuration can be exposed to unauthorized parties.

MitigationUpgrade GitLab to version 17.1.7, 17.2.5, or 17.3.2 or later to patch the password disclosure in repository mirror settings.

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:>= 15.10.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
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. Identify installed GitLab version
    Run `sudo gitlab-rake gitlab:version` or check /opt/gitlab/embedded/service/gitlab-rails/VERSION file
    Affected if Version falls within 15.10.0 to 17.1.6, 17.2.0 to 17.2.4, or 17.3.0 to 17.3.1
  2. Verify repository mirrors exist
    Navigate to Admin Area > Repository > Mirrors or use API: `curl -s --header "PRIVATE-TOKEN: <token>" "https://gitlab.example.com/api/v4/projects" | jq '.[] | select(.mirror == true)'`
    Affected if Any project has a repository mirror configured with a password
  3. Inspect mirror credentials in database
    Query the GitLab database: `sudo gitlab-psql -d gitlabhq_production -c "SELECT project_id, remote_uri, password FROM repository_mirrors WHERE password IS NOT NULL;"`
    Affected if Passwords are stored in plain text in the repository_mirrors table (vulnerable behavior)
  4. Check mirror configuration files
    Review /var/opt/gitlab/gitlab-rails/etc/gitlab.yml or project CI/CD settings for hardcoded credentials in mirror URLs (e.g., https://user:[email protected]/repo.git)
    Affected if Credentials appear in plain text within mirror URLs or configuration

You are affected if your GitLab version is within the affected range AND you have configured repository mirrors that store or transmit passwords.

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 GitLab to version 17.1.7, 17.2.5, or 17.3.2 or later to patch the password disclosure in repository mirror settings.

Recommended fix High confidence

17.3.2 or later (latest stable 17.x release)

  1. 1. Back up your GitLab database and repositories before starting the upgrade
  2. 2. Schedule a maintenance window for the upgrade process
  3. 3. Review GitLab's official upgrade documentation for your current version
  4. 4. Upgrade GitLab to version 17.1.7, 17.2.5, or 17.3.2 (or later). For most users, upgrading to the latest stable 17.x release (17.3.2 or newer) is recommended
  5. 5. Run 'gitlab-rake gitlab:env:info' to verify the new version is running
  6. 6. Check GitLab audit logs for any unauthorized access to repository mirror configurations that may have occurred before the patch
  7. 7. Consider rotating passwords that may have been exposed in repository mirror configurations
Caveat Standard GitLab minor/patch upgrades typically have minimal breaking changes; however, review the release notes for your target version for any configuration or API 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-5435 — 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-5435 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