dbcve.org
GitLabApplication

CVE-2024-3958

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 →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 before 17.0.6, 17.1 prior to 17.1.4, and 17.2 prior to 17.2.2. An issue was found that allows someone to abuse a discrepancy between the Web application display and the git command line interface to social engineer victims into cloning non-trusted code.

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 is a UI deception/social engineering vulnerability in GitLab where the web application displays repository information differently from what the git command line interface would show. Attackers can exploit this discrepancy to trick users into cloning malicious code by making the web UI appear trustworthy while the actual git operation fetches different content.

MitigationUpgrade GitLab to version 17.0.6, 17.1.4, 17.2.2 or later to resolve the web-to-CLI discrepancy that enables this social engineering attack.

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:< 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
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 GitLab version in the web UI
    Log into the GitLab web interface and look at the footer of any page. The version number is displayed there in the format 'GitLab version X.Y.Z'.
    Affected if The displayed version falls within one of these ranges: < 17.0.6, >= 17.1.0 and < 17.1.4, or >= 17.2.0 and < 17.2.2
  2. Check GitLab version via command line
    Run `gitlab-rake gitlab:env:info` on the GitLab server or use `gitlab --version` if the CLI tool is installed. This displays the exact GitLab version installed on the host.
    Affected if The reported version number is less than 17.0.6, between 17.1.0 and 17.1.3 inclusive, or between 17.2.0 and 17.2.1 inclusive
  3. Check GitLab version via API
    Send an authenticated GET request to the GitLab API endpoint `/api/v4/version`. For example: `curl -s https://your-gitlab-instance/api/v4/version | jq .`
    Affected if The JSON response contains a version string that matches the vulnerable ranges listed above
  4. Confirm social engineering exposure
    This vulnerability allows attackers to display different content in the web UI versus what the git CLI retrieves. Users who rely on the web UI to verify repository trustworthiness before cloning are exposed. Check if your GitLab instance hosts public or internal repositories accessible to untrusted users.
    Affected if The GitLab version is vulnerable AND the instance hosts repositories that users might clone based on web UI appearance alone

You are affected if your GitLab installation version is < 17.0.6, between 17.1.0-17.1.3, or between 17.2.0-17.2.1.

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, 17.2.2 or later to resolve the web-to-CLI discrepancy that enables this social engineering attack.

Recommended fix High confidence

17.2.2 or later (latest 17.x stable release)

  1. Upgrade GitLab to version 17.0.6 or later (if currently on 16.x)
  2. OR upgrade to version 17.1.4 or later (if currently on 17.1.x)
  3. OR upgrade to version 17.2.2 or later (if currently on 17.2.x)
  4. After upgrade, verify the instance is running the patched version via Help > Version
Caveat Upgrading between major GitLab versions may require database migrations; review GitLab upgrade guides for your current version

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

Fix this in GitLab Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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