dbcve.org
GitLabApplication

CVE-2024-9623

MEDIUM · 6.5 CVSS v3.1 Published 2024-10-10
Fix available
A fix is available. Upgrade to 17.2.9 / 17.3.5 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 was discovered in GitLab CE/EE affecting all versions starting from 8.16 prior to 17.2.9, starting from 17.3 prior to 17.3.5, and starting from 17.4 prior to 17.4.2, which allows deploy keys to push to an archived repository.

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

This is an authorization bypass vulnerability in GitLab CE/EE where deploy keys (typically read-only credentials) can push changes to archived repositories, which should be read-only. This allows unintended write access to repositories that have been archived for preservation.

MitigationUpgrade GitLab to version 17.2.9, 17.3.5, 17.4.2 or later. No configuration workaround exists; the fix is in the GitLab code itself.

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:>= 8.16.0, < 17.2.9>= 17.3.0, < 17.3.5>= 17.4.0, < 17.4.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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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. Determine the installed GitLab version
    Run `gitlab-rake gitlab:env:info` or access the Admin Area > Settings > Applications page, or visit the /help page on your GitLab instance
    Affected if The displayed version falls within 8.16.0 to 17.2.8, 17.3.0 to 17.3.4, or 17.4.0 to 17.4.1
  2. Identify archived repositories in the instance
    As an administrator, use the API or navigate to Projects > Archived or run a search query for archived projects in the admin interface
    Affected if Any repositories have been archived for preservation (the archive checkbox was selected)
  3. Verify deploy keys are configured
    Navigate to Admin Area > Deploy Keys, or check project/repository settings for attached deploy keys
    Affected if One or more deploy keys are active in the GitLab instance
  4. Confirm deploy keys have push permissions to archived repos
    Review which deploy keys are granted write access and are attached to archived repositories by checking the project deploy keys settings
    Affected if A deploy key with push (write) permissions is attached to any archived repository

You are affected if your GitLab version is in the vulnerable range AND you have archived repositories with deploy keys that have push access enabled.

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.2.9 / 17.3.5 / 17.4.2 or later
Fixed in 17.2.917.3.517.4.2
Interim mitigation

Upgrade GitLab to version 17.2.9, 17.3.5, 17.4.2 or later. No configuration workaround exists; the fix is in the GitLab code itself.

Recommended fix High confidence

GitLab 17.4.2 (or 17.3.5 / 17.2.9 depending on current version branch)

  1. 1. Backup your GitLab instance data and configuration
  2. 2. Review GitLab upgrade documentation for your deployment method (omnibus, source, etc.)
  3. 3. Identify your current GitLab version by navigating to Admin Area > Metrics and Profiling > Version
  4. 4. Plan appropriate upgrade path based on your current version
  5. 5. For versions 8.16.0 to 17.2.x: upgrade to GitLab 17.2.9 or later (preferably 17.4.2)
  6. 6. For versions 17.3.0 to 17.3.x: upgrade to GitLab 17.3.5 or later (preferably 17.4.2)
  7. 7. For versions 17.4.0 to 17.4.1: upgrade to GitLab 17.4.2
  8. 8. Execute the upgrade following GitLab's official upgrade instructions
Caveat Review GitLab 17.x release notes for any breaking changes between your current version and 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-9623 — 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-9623 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