dbcve.org
GitLabApplication

CVE-2024-4784

MEDIUM · 5.4 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 →
60/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 EE starting from version 16.7 before 17.0.6, version 17.1 before 17.1.4 and 17.2 before 17.2.2 that allowed bypassing the password re-entry requirement to approve a policy.

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 EE versions 16.7 through 17.2.1 contained an authentication bypass allowing users to approve security policies without re-entering their password, defeating a security control intended to require explicit re-authentication for sensitive policy approvals.

MitigationUpgrade GitLab EE to version 17.0.6, 17.1.4, or 17.2.2 or later to resolve the password re-entry bypass.

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:>= 16.7.0, < 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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. Confirm GitLab edition is Enterprise Edition
    Run `grep -E '^gitlab-ee|^gitlab-ee' /opt/gitlab/version-manifest.txt` or check the UI at Admin Area > Monitoring > Version. This vulnerability only affects GitLab EE, not CE.
    Affected if The instance is GitLab Enterprise Edition (EE)
  2. Identify installed GitLab version
    Run `gitlab-rake gitlab:env:info` or check Admin Area > Monitoring > Version. Note the exact version number (e.g., 17.2.1, 16.11.0).
    Affected if Version falls within ranges: 16.7.0 to 17.0.5, 17.1.0 to 17.1.3, or 17.2.0 to 17.2.1
  3. Verify if Security Policies are configured
    Navigate to the project's Security Dashboard or go to Menu > Secure > Security Policies. Check if any approval security policies are defined.
    Affected if Approval security policies exist in any project on the instance
  4. Test password re-entry requirement for policy approvals
    As a user with permission to approve security policies, attempt to approve a merge request that requires security policy approval. Observe whether the system prompts for password re-authentication or approves immediately.
    Affected if Policy approval completes without prompting for password re-authentication

A GitLab EE instance is affected if it runs version 16.7.0-17.0.5, 17.1.0-17.1.3, or 17.2.0-17.2.1 AND has approval security policies configured AND users can approve without password re-entry.

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 EE to version 17.0.6, 17.1.4, or 17.2.2 or later to resolve the password re-entry bypass.

Recommended fix High confidence

17.0.6, 17.1.4, or 17.2.2

  1. Determine your GitLab installation type (Omnibus, source, Docker, or Helm chart)
  2. For Omnibus installations: Run 'sudo apt-get update' and 'sudo apt-get install gitlab-ee' (or 'gitlab-ce') to upgrade to the latest fixed version
  3. For Docker installations: Pull the new image with 'docker pull gitlab/gitlab-ee:17.2.2' (or desired fixed version) and recreate the container
  4. For Helm chart deployments: Update your Helm values to use the new GitLab version and run 'helm upgrade'
  5. For source installations: Check out the release tag 'v17.2.2' from the GitLab repository and rebuild
  6. After upgrade, verify the GitLab version matches one of the fixed releases: 17.0.6, 17.1.4, or 17.2.2
  7. Test that the password re-entry requirement is now properly enforced when approving policies

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

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.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-4784 — 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-4784 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