Loop with Unreachable Exit Condition ('Infinite Loop') in GitLab
2 public exploits exists; no exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in GitLab 16.3.6, GitLab 16.4.2 and GitLab 16.5.1.
An issue has been discovered in GitLab CE/EE affecting all versions starting from 16.2 before 16.3.6, all versions starting from 16.4 before 16.4.2, all versions starting from 16.5 before 16.5.1. A low-privileged attacker can point a CI/CD Component to an incorrect path and cause the server to exhaust all available memory through an infinite loop and cause Denial of Service.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| GitLab | GitLab | >=16.2 <16.3.6, >=16.4 <16.4.2, >=16.5 <16.5.1 | 16.3.6, 16.4.2, 16.5.1 |
Exploit evidence
2 public sources
Vendor advisories
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in GitLab, strongest first
Embed
A live severity badge for an advisory, README or ticket