dbcve.org
GitLabApplication

CVE-2024-7404

MEDIUM · 6.5 CVSS v3.1 Published 2024-11-14
Fix available
A fix is available. Upgrade to 17.3.7 / 17.4.4 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 17.2 prior to 17.3.7, starting from 17.4 prior to 17.4.4 and starting from 17.5 prior to 17.5.2, which could have allowed an attacker gaining full API access as the victim via the Device OAuth flow.

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

A vulnerability in GitLab's Device OAuth flow across versions 17.2 through 17.5.2 allows an attacker to potentially hijack the OAuth authorization process and gain full API access as the victim user, enabling privilege escalation to impersonate the victim.

MitigationUpgrade GitLab to version 17.3.7, 17.4.4, 17.5.2 or later to patch the OAuth flow vulnerability.

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:>= 17.2.0, < 17.3.7>= 17.4.0, < 17.4.4>= 17.5.0, < 17.5.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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 `/opt/gitlab/version` to obtain the exact version number
    Affected if The installed version falls within 17.2.0 to 17.3.6, 17.4.0 to 17.4.3, or 17.5.0 to 17.5.1
  2. Verify Device OAuth is enabled
    Check GitLab admin settings at /admin/application_settings or via API endpoint `/api/v4/application/settings` for the `device_flow_enabled` setting
    Affected if Device OAuth flow (device_flow_enabled) is set to true in GitLab settings
  3. Review active OAuth device authorizations
    Query the database for recent device_flow_authorizations table entries: `sudo gitlab-psql -d gitlabhq_production -c "SELECT user_id, device_flow_id, created_at FROM device_flow_authorizations WHERE created_at > NOW() - INTERVAL '7 days' ORDER BY created_at DESC;"`
    Affected if There are unexpected or unauthorized device authorization entries in the authorization logs

You are affected if your GitLab version is 17.2.0-17.3.6, 17.4.0-17.4.3, or 17.5.0-17.5.1 AND Device OAuth flow is enabled in your instance.

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.3.7 / 17.4.4 / 17.5.2 or later
Fixed in 17.3.717.4.417.5.2
Interim mitigation

Upgrade GitLab to version 17.3.7, 17.4.4, 17.5.2 or later to patch the OAuth flow vulnerability.

Recommended fix High confidence

17.5.2 (or later 17.x release)

  1. Backup your GitLab instance data and configuration before upgrading
  2. Review GitLab upgrade documentation for your installation method (Omnibus, source, etc.)
  3. Ensure your current version is one of the affected versions: 17.2.0-17.3.6, 17.4.0-17.4.3, or 17.5.0-17.5.1
  4. Plan your upgrade path following GitLab's recommended upgrade path based on your current version
  5. For Omnibus installations: Run 'gitlab-ctl stop' before upgrade, then upgrade using your package manager
  6. For source installations: Stop GitLab services, download the fixed release, update the files, and run database migrations
  7. After upgrade, verify GitLab is running: 'gitlab-ctl status' or check the web interface
  8. Confirm the Device OAuth flow is now properly secured and test OAuth functionality
Caveat Standard GitLab upgrade considerations apply - review release notes for your target version for any specific breaking changes or required manual steps

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

Fix this in GitLab Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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