Skip to main content
Vulnerability Database/CVE-2024-11668

CVE-2024-11668: GitLab Authentication Bypass Vulnerability

CVE-2024-11668 is an authentication bypass flaw in GitLab CE/EE affecting versions 16.11 to 17.6. Long-lived connections can bypass authentication controls, enabling unauthorized access to streaming results. This article covers technical details, affected versions, impact assessment, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2024-11668 Overview

CVE-2024-11668 affects GitLab Community Edition (CE) and Enterprise Edition (EE) across multiple release branches. The flaw allows long-lived connections to bypass authentication controls and access streaming results without authorization. GitLab assigned a medium severity rating based on confidentiality impact only, with no integrity or availability consequences.

The vulnerability spans GitLab versions 16.11 through 17.4.5, 17.5 before 17.5.3, and 17.6 before 17.6.1. The weakness is tracked under CWE-613 (Insufficient Session Expiration). Both self-managed and enterprise deployments are affected.

Critical Impact

Unauthenticated network attackers can access streaming results through persistent connections that outlive their authentication session, exposing confidential data from affected GitLab instances.

Affected Products

  • GitLab Community Edition (CE) versions 16.11 through 17.4.5
  • GitLab Enterprise Edition (EE) versions 17.5 before 17.5.3
  • GitLab CE/EE version 17.6.0 before 17.6.1

Discovery Timeline

  • 2024-11-26 - CVE-2024-11668 published to the National Vulnerability Database (NVD)
  • 2026-06-17 - Last updated in NVD database

Technical Details for CVE-2024-11668

Vulnerability Analysis

The vulnerability resides in how GitLab manages session state for long-lived connections. Streaming endpoints maintain persistent connections to deliver incremental results to clients. These connections do not re-validate the caller's authentication state once established.

An attacker who obtains or maintains a long-lived connection can continue consuming streaming output after their session should have expired. The flaw is classified under CWE-613, which covers insufficient session expiration conditions. Exploitation requires no privileges and no user interaction.

The impact is limited to information disclosure. Attackers cannot modify data or disrupt service availability through this flaw. However, streamed job output, logs, and build artifacts may contain secrets, source code excerpts, or infrastructure details.

Root Cause

The root cause is improper enforcement of session lifetime on streaming response handlers. GitLab's authentication middleware validates credentials at connection initiation but does not re-check authorization state during the lifetime of the stream. Long-lived HTTP responses therefore continue delivering data past the point at which authentication should be revoked.

Attack Vector

The attack vector is network-based and does not require authentication at the point of exploitation. An attacker establishes a connection to a streaming endpoint and keeps it open. When session invalidation events occur, the stream continues delivering data because the server does not terminate active connections tied to expired sessions. See the GitLab Issue #456922 tracker for coordinated disclosure details.

No verified public proof-of-concept code is available for this vulnerability. The technical mechanism involves exploiting the gap between session termination and connection termination on streaming routes.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2024-11668

Indicators of Compromise

  • Unusually long-lived HTTP connections to GitLab streaming endpoints such as job trace or build log routes
  • Streaming responses continuing past known session logout or token revocation events
  • Repeated connections to streaming endpoints from clients that did not complete standard authentication flows
  • Access to job artifacts or trace data from source IPs with no corresponding authenticated session records

Detection Strategies

  • Correlate web server access logs against application session termination events to identify streams that outlive their session
  • Alert on HTTP response durations to streaming endpoints that exceed configured session timeout thresholds
  • Review GitLab audit logs for streaming resource access without matching login records in the same window

Monitoring Recommendations

  • Monitor reverse proxy or load balancer metrics for connections to GitLab endpoints held open beyond expected intervals
  • Ingest GitLab application and NGINX logs into a centralized analytics platform to baseline normal streaming connection lifetimes
  • Track anomalous access patterns to CI/CD job output endpoints, which commonly expose secrets if leaked

How to Mitigate CVE-2024-11668

Immediate Actions Required

  • Upgrade GitLab CE/EE to version 17.4.5, 17.5.3, 17.6.1, or later as applicable to your release branch
  • Rotate any credentials, tokens, or secrets that may have been exposed through CI/CD job traces during the vulnerable window
  • Audit active sessions and terminate long-lived connections to streaming endpoints after upgrading

Patch Information

GitLab released fixed versions 17.4.5, 17.5.3, and 17.6.1 that enforce session re-validation on streaming connections. Administrators should apply the appropriate patched release for their deployment branch. Consult the GitLab Issue #456922 reference for release-specific guidance.

Workarounds

  • Configure upstream reverse proxies (NGINX, HAProxy) to enforce maximum connection duration limits on GitLab streaming routes
  • Reduce session and personal access token lifetimes to shrink the window during which long-lived connections remain valid
  • Restrict network access to GitLab instances using IP allowlists where feasible until patches are applied
bash
# NGINX example: cap long-lived upstream connections to GitLab
proxy_read_timeout 300s;
proxy_send_timeout 300s;
keepalive_timeout 60s;
send_timeout 60s;

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.