dbcve.org
GitLabApplication

CVE-2024-9183

MEDIUM · 6.4 CVSS v3.1 Published 2025-12-05
Fix available
A fix is available. Upgrade to 18.4.5 / 18.5.3 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable

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
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.4 prior to 18.4.5, 18.5 prior to 18.5.3, and 18.6 prior to 18.6.1 that could have allowed an authenticated user to obtain credentials from higher-privileged users and perform actions in their context under specific conditions.

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 · moderate confidence

An authenticated user could obtain credentials from higher-privileged users in GitLab CE/EE versions 18.4 prior to 18.4.5, 18.5 prior to 18.5.3, and 18.6 prior to 18.6.1, enabling them to perform actions in the higher-privileged user's context under specific conditions.

MitigationUpgrade GitLab to version 18.4.5, 18.5.3, 18.6.1 or later. Alternatively, if immediate upgrade is not feasible, review user permissions and audit access logs for suspicious credential access patterns.

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:>= 18.4.0, < 18.4.5>= 18.5.0, < 18.5.3>= 18.6.0, < 18.6.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
High
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/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. Check installed GitLab version
    Run command: sudo gitlab-rake gitlab:env:info or check /opt/gitlab/version file
    Affected if Version falls within 18.4.0 through 18.4.4, 18.5.0 through 18.5.2, or 18.6.0 through 18.6.0
  2. Confirm exact version number
    Run: sudo gitlab-rake gitlab:git_version to get precise version
    Affected if Version is less than 18.4.5, 18.5.3, or 18.6.1 respectively for each branch
  3. Identify user role configuration
    Review which authenticated user roles exist in the GitLab instance via Admin Area > Users section
    Affected if Multiple privilege levels exist and lower-privileged users have API or web access
  4. Check audit logs for credential access
    Navigate to Admin Area > Audit Events and filter for credential-related events or examine user session creation events
    Affected if Unexpected credential or session creation events from lower-privileged accounts appear in logs

You are affected if your GitLab version is 18.4.0-18.4.4, 18.5.0-18.5.2, or 18.6.0-18.6.0 and you have users with varying privilege levels using the system.

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.4.5 / 18.5.3 / 18.6.1 or later
Fixed in 18.4.518.5.318.6.1
Interim mitigation

Upgrade GitLab to version 18.4.5, 18.5.3, 18.6.1 or later. Alternatively, if immediate upgrade is not feasible, review user permissions and audit access logs for suspicious credential access patterns.

Recommended fix High confidence

Upgrade to GitLab 18.4.5, 18.5.3, or 18.6.1 (or later stable releases) based on your current branch

  1. Identify your current GitLab version from the admin dashboard or using `sudo gitlab-rake gitlab:env:info`
  2. Determine which version range you are in (18.4.x, 18.5.x, or 18.6.x)
  3. Create a full backup of your GitLab instance using `sudo gitlab-backup-create`
  4. Stop GitLab services with `sudo gitlab-ctl stop`
  5. Update your package manager and install the fixed version: On Debian/Ubuntu run `sudo apt-get update && sudo apt-get install gitlab-ee` (or `gitlab-ce`); On RHEL/CentOS run `sudo yum install gitlab-ee` (or `gitlab-ce`)
  6. Reconfigure GitLab with `sudo gitlab-ctl reconfigure`
  7. Restart GitLab with `sudo gitlab-ctl restart`
  8. Verify the upgrade was successful and the version matches 18.4.5, 18.5.3, 18.6.1, or later
Caveat Standard GitLab upgrade considerations apply - review release notes for any major changes between your current and target version

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

Fix this in GitLab Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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