A path traversal vulnerability in GitLab CE/EE allows authenticated attackers to bypass security restrictions, posing a high risk of unauthorized system access.

This vulnerability is a path traversal flaw (CWE-22) residing in the GitLab platform. An authenticated attacker with low privileges can exploit this to escape restricted directories, which may result in unauthorized file system access or manipulation.

Successful exploitation of this path traversal vulnerability could lead to the exposure of sensitive configuration files, source code, or internal system data. Given the CVSS score of 8.5, this high-severity flaw threatens the confidentiality, integrity, and availability of the GitLab environment, potentially leading to full system compromise depending on the targeted files.

Immediate Action: Upgrade all GitLab CE/EE instances to versions 19.0.6, 19.1.4, 19.2.2, or above immediately.

Proactive Monitoring: Review application access logs for suspicious path traversal patterns, such as the use of double dots or unexpected directory structures in file-related requests.

Compensating Controls: Deploy or update Web Application Firewall rules to detect and block directory traversal payloads targeting the GitLab web interface.

Public Exploit Available: Yes, a public proof-of-concept exists on GitHub.

The presence of a public proof-of-concept increases the likelihood of exploitation by threat actors. Administrators must prioritize the application of the vendor-provided security patches to the specified GitLab versions to eliminate this risk immediately.