CVE-2024-2434

8.5 HIGH

📋 TL;DR

This CVE describes a path traversal vulnerability in GitLab that allows attackers to access restricted files and potentially cause denial of service. The vulnerability affects all GitLab Community Edition and Enterprise Edition installations running vulnerable versions. Attackers could read sensitive files they shouldn't have access to.

💻 Affected Systems

Products:
  • GitLab Community Edition
  • GitLab Enterprise Edition
Versions: 16.9 prior to 16.9.6, 16.10 prior to 16.10.4, 16.11 prior to 16.11.1
Operating Systems: All platforms running GitLab
Default Config Vulnerable: ⚠️ Yes
Notes: All deployments of affected versions are vulnerable 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

Complete system compromise through reading sensitive configuration files, credentials, or source code, potentially leading to further attacks and data exfiltration.

🟠

Likely Case

Unauthorized reading of restricted files containing sensitive information, potentially exposing credentials, configuration details, or proprietary code.

🟢

If Mitigated

Limited impact with proper access controls and monitoring, though the vulnerability still exists in the codebase.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires some knowledge of GitLab's file structure and path traversal techniques.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 16.9.6, 16.10.4, or 16.11.1

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

Restart Required: Yes

Instructions:

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

🔧 Temporary Workarounds

Restrict network access

all

Limit access to GitLab instance to trusted networks only

Implement WAF rules

all

Add web application firewall rules to detect and block path traversal attempts

🧯 If You Can't Patch

  • Implement strict network segmentation and limit GitLab access to authorized users only
  • Enable enhanced logging and monitoring for file access patterns and path traversal attempts

🔍 How to Verify

Check if Vulnerable:

Check GitLab version via admin panel or run: sudo gitlab-rake gitlab:env:info | grep 'GitLab version'

Check Version:

sudo gitlab-rake gitlab:env:info | grep 'GitLab version'

Verify Fix Applied:

Verify version is 16.9.6, 16.10.4, or 16.11.1 or higher

📡 Detection & Monitoring

Log Indicators:

  • Unusual file access patterns
  • Requests with '../' sequences
  • Access to restricted file paths

Network Indicators:

  • Multiple failed file access attempts
  • Requests to unusual file paths

SIEM Query:

source="gitlab" AND (path="*../*" OR uri="*../*")

🔗 References

📤 Share & Export