dbcve.org
GitLabApplication

CVE-2024-12380

HIGH · 7.5 CVSS v3.1 Published 2025-03-13
Fix available
A fix is available. Upgrade to 17.7.7 / 17.8.5 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 EE/CE affecting all versions starting from 11.5 before 17.7.7, all versions starting from 17.8 before 17.8.5, all versions starting from 17.9 before 17.9.2. Certain user inputs in repository mirroring settings could potentially expose sensitive authentication information.

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

This GitLab vulnerability in repository mirroring settings allows exposure of sensitive authentication information (credentials, tokens, or SSH keys used for repository mirroring) through certain user inputs. The issue affects all versions from 11.5 through the 17.x branch prior to the fixed releases.

MitigationUpgrade GitLab to version 17.7.7, 17.8.5, or 17.9.2 (or later) to remediate the authentication information exposure in repository mirroring 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:>= 11.5.0, < 17.7.7>= 17.8.0, < 17.8.5>= 17.9.0, < 17.9.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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
    Log into the GitLab administration area and navigate to the version information page, or run 'sudo gitlab-rake gitlab:env:info' on the server to retrieve the exact version number
    Affected if The version falls within any of these ranges: 11.5.0 to 17.7.6, 17.8.0 to 17.8.4, or 17.9.0 to 17.9.1
  2. Check if repository mirroring is configured
    Navigate to a project's Settings > Repository > Mirroring repositories (or access via Admin Area > Projects > mirroring settings) to see if any mirror configurations exist
    Affected if Repository mirroring is actively configured with credentials, tokens, or SSH keys for external repositories
  3. Verify repository mirroring credentials are visible
    Edit an existing repository mirror configuration and inspect whether sensitive authentication fields (password/token/SSH key) are displayed in plain text or pre-populated in input fields when viewing the mirror settings
    Affected if Credentials, tokens, or SSH keys used for mirroring are exposed in the UI or accessible through the mirroring settings interface

A user is affected if their GitLab version is within the vulnerable ranges AND repository mirroring is configured with stored credentials, tokens, or SSH keys that could be exposed through the mirroring settings interface.

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.7.7 / 17.8.5 / 17.9.2 or later
Fixed in 17.7.717.8.517.9.2
Interim mitigation

Upgrade GitLab to version 17.7.7, 17.8.5, or 17.9.2 (or later) to remediate the authentication information exposure in repository mirroring settings.

Recommended fix High confidence

17.9.2 (latest stable fixed release)

  1. Identify your current GitLab version using `gitlab-rake gitlab:env:info`
  2. Determine which version branch you need to upgrade to based on your current version
  3. For versions 11.5.0 to 17.6.x: upgrade to 17.7.7
  4. For versions 17.7.x: upgrade to 17.7.7
  5. For versions 17.8.0 to 17.8.4: upgrade to 17.8.5
  6. For versions 17.9.0 to 17.9.1: upgrade to 17.9.2
  7. Perform a full backup of your GitLab instance before upgrading using `gitlab-backup create`
  8. Update GitLab using your package manager (e.g., `apt-get update && apt-get install gitlab-ce` or equivalent for your package)
Caveat Review GitLab upgrade guides for any version-specific migration notes; major version jumps may require additional steps

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