dbcve.org
GitLabApplication

CVE-2024-7091

MEDIUM · 5.0 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 →
56/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 was discovered in GitLab CE/EE affecting all versions starting from 15.6 prior to 17.0.5, starting from 17.1 prior to 17.1.3, and starting from 17.2 prior to 17.2.1 where it was possible to disclose limited information of an exported group or project to another user.

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 contains an information disclosure vulnerability in the group and project export functionality. Due to improper access controls, a user can potentially view limited information about exports of groups or projects they should not have access to, allowing unauthorized disclosure of metadata about exported content.

MitigationUpdate GitLab to version 17.0.5, 17.1.3, 17.2.1 or later to patch the vulnerability. Follow standard GitLab upgrade procedures for your deployment model.

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, < 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
Changed
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/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 `gitlab-rake gitlab:env:info` or query the API at `/api/v4/version`, or check the Admin area > Monitoring > Version page
    Affected if The version falls within any of these ranges: >= 15.6 and < 17.0.5; >= 17.1 and < 17.1.3; >= 17.2 and < 17.2.1
  2. Verify group/project export feature is accessible
    Confirm the export feature is not disabled. Check admin settings at Admin > Settings > Export and general settings, or inspect `gitlab_rails['export_group_enabled']` and `gitlab_rails['export_project_enabled']` in /etc/gitlab/gitlab.rb
    Affected if Export functionality is enabled (default) and version is vulnerable per step 1
  3. Check for unauthorized export metadata access attempts
    Review GitLab audit logs for entries containing 'export' and 'group' or 'project' in Admin > Monitoring > Audit Events, or grep audit logs for export-related events showing access to exports outside user's permissions
    Affected if Audit logs show export metadata access events for groups/projects the querying user does not have export permissions for

You are affected if your GitLab version is 15.6 through 17.0.4, 17.1.0 through 17.1.2, or 17.2.0, and the group/project export feature is enabled (default).

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

Update GitLab to version 17.0.5, 17.1.3, 17.2.1 or later to patch the vulnerability. Follow standard GitLab upgrade procedures for your deployment model.

Recommended fix High confidence

Upgrade to GitLab 17.0.5, 17.1.3, 17.2.1, or later (recommended: 17.2.1 or latest 17.x release)

  1. 1. Identify the currently running GitLab version using `sudo gitlab-rake gitlab:env:info` or checking the GitLab admin area.
  2. 2. Determine the appropriate upgrade path based on current version: if on 15.6-16.x, plan to upgrade to 17.0.5 or later; if on 17.0.x, upgrade to 17.0.5; if on 17.1.x, upgrade to 17.1.3; if on 17.2.x, upgrade to 17.2.1.
  3. 3. Review the GitLab upgrade documentation for your current version to ensure compatibility with the target version.
  4. 4. Create a full backup of the GitLab instance using `sudo gitlab-backup-create` before proceeding.
  5. 5. Update the GitLab package using the appropriate method for your installation (omnibus package, source install, or GitLab Helm chart).
  6. 6. After upgrade, run `sudo gitlab-ctl reconfigure` and verify the new version is running.
  7. 7. Verify the vulnerability is resolved by confirming the GitLab version matches or exceeds 17.0.5, 17.1.3, or 17.2.1 depending on your upgrade path.
Caveat Upgrading across major GitLab versions (e.g., 15.x to 17.x) may introduce breaking changes; review the GitLab upgrade guides for any required migration steps

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
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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