dbcve.org
GitLabApplication

CVE-2024-7060

MEDIUM · 6.5 CVSS v3.1 Published 2024-07-24
Fix available
A fix is available. Upgrade to 17.0.5 / 17.1.3 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 information disclosure vulnerability in GitLab CE/EE in project/group exports affecting all versions from 15.4 prior to 17.0.5, 17.1 prior to 17.1.3, and 17.2 prior to 17.2.1 allows unauthorized users to view the resultant export.

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

An access control flaw in GitLab's project and group export functionality allows unauthenticated or unauthorized users to access export files they should not be able to view. The export generation process does not properly validate requester permissions before serving the exported data.

MitigationUpgrade GitLab to versions 17.0.5, 17.1.3, 17.2.1 or later. Review export access controls and audit recent export activity for unauthorized access.

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.4, < 17.0.5>= 17.1, < 17.1.3>= 17.2, < 17.2.1

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 panel under Help > Version. Alternatively, check the /opt/gitlab/version file.
    Affected if The installed version falls within 15.4 to 17.0.4, 17.1.0 to 17.1.2, or 17.2.0.
  2. Verify project export feature is enabled
    Navigate to Admin Area > Settings > Visibility and access controls > scroll to Export project. Check if project export is enabled, or query the database: `sudo gitlab-rails console` then `ProjectExportState.any_export_enabled?`
    Affected if Project or group export is enabled in the GitLab instance settings.
  3. Inspect audit logs for export-related access
    Check GitLab audit logs under Admin Area > Audit Events. Filter for event types like 'export_download' or 'export_file_download'. Look for downloads by users without proper project/group membership.
    Affected if Audit logs show export file downloads by unauthenticated users or users lacking project/group access.
  4. Review export file storage permissions
    Examine the export storage directory (default: /var/opt/gitlab/gitlab-rails/shared/exports). Verify that exported files are not directly accessible via web without authentication. Check the nginx configuration for export-related paths.
    Affected if Export files are served without proper permission validation or are accessible via direct URL without auth.

The environment is affected if GitLab version is within the affected ranges AND project/group export functionality is enabled, with potential evidence of unauthorized access in audit logs.

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.5 / 17.1.3 / 17.2.1 or later
Fixed in 17.0.517.1.317.2.1
Interim mitigation

Upgrade GitLab to versions 17.0.5, 17.1.3, 17.2.1 or later. Review export access controls and audit recent export activity for unauthorized access.

Recommended fix High confidence

17.0.5, 17.1.3, or 17.2.1 (depending on your current version)

  1. Backup your GitLab instance data before proceeding with the upgrade
  2. Determine your current GitLab version by checking the Admin Area > Settings > Metrics and profiling > Version
  3. If running >= 15.4 and < 17.0.5: upgrade to GitLab 17.0.5
  4. If running >= 17.1 and < 17.1.3: upgrade to GitLab 17.1.3
  5. If running >= 17.2 and < 17.2.1: upgrade to GitLab 17.2.1
  6. After upgrade, verify the GitLab instance is functioning correctly
  7. Review export functionality to confirm the vulnerability is remediated
Caveat Standard GitLab upgrade considerations apply; review release notes for any between-version 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-7060 — 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-7060 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