dbcve.org
GitLabApplication

CVE-2024-10219

MEDIUM · 6.5 CVSS v3.1 Published 2025-08-13
Fix available
A fix is available. Upgrade to 18.0.6 / 18.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 from 15.6 before 18.0.6, 18.1 before 18.1.4, and 18.2 before 18.2.2 that under certain conditions could have allowed authenticated users to bypass access controls and download private artifacts by accessing specific API endpoints.

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 CE/EE versions prior to 18.0.6, 18.1.4, and 18.2.2 contain an access control bypass vulnerability in specific API endpoints that allows authenticated users to download private artifacts they should not have access to, exploiting insufficient permission validation under certain conditions.

MitigationUpgrade GitLab to version 18.0.6, 18.1.4, 18.2.2 or later. After upgrading, verify that artifact access controls properly restrict unauthorized downloads through the affected API endpoints.

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.6.0, < 18.0.6>= 18.1.0, < 18.1.4>= 18.2.0, < 18.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 `sudo gitlab-rake gitlab:env:info` or check the GitLab admin area under /admin/about. Alternatively, check the package version with `dpkg -l | grep gitlab-ee` (Debian/Ubuntu) or `rpm -qa | grep gitlab` (RHEL/CentOS).
    Affected if The version displayed is prior to 18.0.6, between 18.1.0-18.1.3, or between 18.2.0-18.2.1 (for GitLab versions 15.6.0 and above)
  2. Confirm GitLab edition (CE or EE)
    Check if the installation is Community Edition (CE) or Enterprise Edition (EE) using `sudo gitlab-rake gitlab:git:version` or by examining the license information in the admin panel.
    Affected if The edition is CE or EE and the version falls within the affected ranges listed in step 1
  3. Identify if artifact API endpoints are reachable
    Locate the API endpoint paths related to artifact downloads. These typically follow patterns such as `/api/v4/projects/:id/jobs/:job_id/artifacts` or similar artifact retrieval endpoints. Verify these endpoints are accessible within the environment.
    Affected if The artifact download API endpoints exist and respond to authenticated requests (this is a prerequisite for the vulnerability to be exploitable)
  4. Verify artifact permission model configuration
    Review the GitLab project and group settings related to artifact access controls. Check if private artifacts are accessible to project members with reporter or guest roles, or if artifact downloads are permitted across project boundaries.
    Affected if Artifact permissions allow downloads by users who should not have access to private artifacts based on project membership or access level

You are affected if your GitLab installation version falls within 15.6.0 to 18.0.5, 18.1.0 to 18.1.3, or 18.2.0 to 18.2.1, and the artifact download API endpoints are accessible to authenticated users who lack proper authorization for the requested artifacts.

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 18.0.6 / 18.1.4 / 18.2.2 or later
Fixed in 18.0.618.1.418.2.2
Interim mitigation

Upgrade GitLab to version 18.0.6, 18.1.4, 18.2.2 or later. After upgrading, verify that artifact access controls properly restrict unauthorized downloads through the affected API endpoints.

Recommended fix High confidence

18.2.2 or latest stable 18.x release

  1. Backup your GitLab data and database before starting the upgrade
  2. Review GitLab release notes for version 18.2.2 (or latest 18.x stable) for any specific migration requirements
  3. Ensure your current GitLab version matches one of the affected versions: 15.6.0 to 18.0.5, 18.1.0 to 18.1.3, or 18.2.0 to 18.2.1
  4. Stop GitLab services before upgrading
  5. Update GitLab to version 18.2.2 or later using your package manager (e.g., apt-get for Ubuntu/Debian, yum for RHEL/CentOS) or the official GitLab upgrade method
  6. After installation, run sudo gitlab-ctl reconfigure to apply changes
  7. Verify the upgrade was successful by checking GitLab version and logging in
  8. Test that the artifact download functionality works correctly with proper authorization enforcement
Caveat Review GitLab 18.x release notes for any breaking changes between your current version and the target version; major version upgrades may require additional migration 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
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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