CVE-2024-11669

6.5 MEDIUM

📋 TL;DR

This vulnerability in GitLab CE/EE allows attackers with valid API tokens to access sensitive data beyond their intended permissions due to overly broad token scopes. It affects all GitLab instances running vulnerable versions, potentially exposing user data, repository contents, or configuration information. The issue stems from improper authorization checks in certain API endpoints.

💻 Affected Systems

Products:
  • GitLab Community Edition
  • GitLab Enterprise Edition
Versions: 16.9.8 to 17.4.4, 17.5.0 to 17.5.2, 17.6.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Affects all deployments of GitLab CE/EE within the specified version ranges regardless of configuration.

📦 What is this software?

Gitlab by Gitlab

GitLab is a complete DevOps platform providing source code management, CI/CD pipelines, security scanning, container registry, and collaboration tools used by millions of developers and thousands of enterprises worldwide. As both a cloud-hosted SaaS offering (GitLab.com) and self-managed software, G...

Learn more about Gitlab →

Gitlab by Gitlab

GitLab is a complete DevOps platform providing source code management, CI/CD pipelines, security scanning, container registry, and collaboration tools used by millions of developers and thousands of enterprises worldwide. As both a cloud-hosted SaaS offering (GitLab.com) and self-managed software, G...

Learn more about Gitlab →

Gitlab by Gitlab

GitLab is a complete DevOps platform providing source code management, CI/CD pipelines, security scanning, container registry, and collaboration tools used by millions of developers and thousands of enterprises worldwide. As both a cloud-hosted SaaS offering (GitLab.com) and self-managed software, G...

Learn more about Gitlab →

Gitlab by Gitlab

GitLab is a complete DevOps platform providing source code management, CI/CD pipelines, security scanning, container registry, and collaboration tools used by millions of developers and thousands of enterprises worldwide. As both a cloud-hosted SaaS offering (GitLab.com) and self-managed software, G...

Learn more about Gitlab →

Gitlab by Gitlab

GitLab is a complete DevOps platform providing source code management, CI/CD pipelines, security scanning, container registry, and collaboration tools used by millions of developers and thousands of enterprises worldwide. As both a cloud-hosted SaaS offering (GitLab.com) and self-managed software, G...

Learn more about Gitlab →

Gitlab by Gitlab

GitLab is a complete DevOps platform providing source code management, CI/CD pipelines, security scanning, container registry, and collaboration tools used by millions of developers and thousands of enterprises worldwide. As both a cloud-hosted SaaS offering (GitLab.com) and self-managed software, G...

Learn more about Gitlab →

⚠️ Risk & Real-World Impact

🔴

Worst Case

Unauthorized access to sensitive user data, source code, credentials, or configuration files leading to data breach, intellectual property theft, or further system compromise.

🟠

Likely Case

Privilege escalation where users with limited API tokens can access resources beyond their intended scope, potentially exposing internal data.

🟢

If Mitigated

Limited impact with proper network segmentation, minimal API token usage, and strict access controls in place.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires a valid API token but can bypass intended scope restrictions. No public exploit code has been released as of analysis.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 17.4.5, 17.5.3, 17.6.1

Vendor Advisory: https://gitlab.com/gitlab-org/gitlab/-/issues/501528

Restart Required: Yes

Instructions:

1. Backup your GitLab instance. 2. Update to GitLab 17.4.5, 17.5.3, or 17.6.1 depending on your current version. 3. Restart GitLab services. 4. Verify the update was successful.

🔧 Temporary Workarounds

Restrict API Token Usage

all

Temporarily disable or restrict API token usage for non-essential operations until patching can be completed.

Review and revoke unnecessary API tokens via GitLab admin interface

Network Access Controls

all

Restrict access to GitLab API endpoints from untrusted networks.

Configure firewall rules to limit GitLab API access to trusted IP ranges only

🧯 If You Can't Patch

  • Implement strict network segmentation to isolate GitLab instances from sensitive networks
  • Audit and rotate all API tokens, implementing principle of least privilege for token scopes

🔍 How to Verify

Check if Vulnerable:

Check GitLab version via Admin Area → Overview or run: sudo gitlab-rake gitlab:env:info | grep 'Version:'

Check Version:

sudo gitlab-rake gitlab:env:info | grep 'Version:'

Verify Fix Applied:

Confirm version is 17.4.5, 17.5.3, or 17.6.1 or higher using the same command

📡 Detection & Monitoring

Log Indicators:

  • Unusual API access patterns
  • API requests from tokens accessing endpoints beyond their scope
  • Failed authorization attempts followed by successful access

Network Indicators:

  • Increased API traffic to sensitive endpoints
  • API requests with unexpected token scopes

SIEM Query:

source="gitlab" AND (event="api_access" OR event="authentication") AND status="success" AND user_scope!="expected_scope"

🔗 References

📤 Share & Export