dbcve.org
GitLabApplication

CVE-2024-3035

HIGH · 8.1 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 →
87/100
Remediation priority · High
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
A permission check vulnerability in GitLab CE/EE affecting all versions starting from 8.12 prior to 17.0.6, 17.1 prior to 17.1.4, and 17.2 prior to 17.2.2 allowed for LFS tokens to read and write to the user owned repositories.

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

A permission check vulnerability in GitLab CE/EE allows LFS (Large File Storage) tokens to bypass intended authorization controls and read/write to user-owned repositories when they should not have access. This is a classic authorization bypass where the LFS token validation fails to properly check repository permissions.

MitigationUpgrade GitLab to version 17.0.6, 17.1.4, or 17.2.2 or later to patch the permission check vulnerability. Alternatively, review and restrict LFS token usage if immediate upgrade is not feasible.

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:>= 8.12.0, < 17.0.6>= 17.1, < 17.1.4>= 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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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. Determine your GitLab installation version
    Run `gitlab-rake gitlab:env:info` or check the GitLab admin interface under Admin Area > Overview > Dashboard. Alternatively, check your package manager: `dpkg -l | grep gitlab-ee` (Debian/Ubuntu) or `rpm -qa | grep gitlab` (RHEL/CentOS).
    Affected if The installed version falls within any of these ranges: >= 8.12.0 and < 17.0.6; >= 17.1.0 and < 17.1.4; >= 17.2.0 and < 17.2.2.
  2. Verify if LFS (Large File Storage) is enabled
    In GitLab admin panel, go to Settings > Repository > Large File Storage (LFS) and check if 'Enable LFS' is toggled on. Alternatively, check for .gitattributes files with 'filter=lfs' entries in your repositories.
    Affected if LFS is enabled and users have LFS tokens configured.
  3. Check for active LFS tokens
    In GitLab, navigate to User Settings > Access Tokens and look for tokens with 'api' or 'read_repository' scopes. LFS operations use these tokens for authentication. You can also query the GitLab database: `sudo gitlab-rails console` then `User.with_identifiers(:lfs_token).each { |u| puts u.username }` to find users with LFS tokens.
    Affected if Users have access tokens being used for LFS operations, particularly with broad repository scopes.
  4. Inspect repository access controls for LFS operations
    Attempt to use an LFS token from one user to access a different user-owned private repository. Check if the operation succeeds when it should fail. Review GitLab audit logs under Admin Area > Monitoring > Audit Events for LFS-related operations.
    Affected if LFS operations can access repositories outside the token owner's authorized scope.

Your environment is affected if you are running a GitLab version within the vulnerable ranges AND have LFS enabled with users possessing access tokens used for LFS operations.

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 to patch the permission check vulnerability. Alternatively, review and restrict LFS token usage if immediate upgrade is not feasible.

Recommended fix High confidence

GitLab 17.0.6, 17.1.4, or 17.2.2 (depending on your current major version)

  1. 1. Backup your GitLab instance data before proceeding with the upgrade.
  2. 2. Identify your current GitLab version by running: gitlab-rake gitlab:env:info
  3. 3. For GitLab 8.12.x through 16.x: Upgrade to GitLab 17.0.6 or later.
  4. 4. For GitLab 17.1.x: Upgrade to GitLab 17.1.4 or later.
  5. 5. For GitLab 17.2.x: Upgrade to GitLab 17.2.2 or later.
  6. 6. After upgrade, verify the GitLab instance is functioning correctly and test LFS functionality.
Caveat Major version upgrades may require database migrations; review GitLab upgrade documentation for compatibility notes between versions

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

Fix this in GitLab Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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