First published: Mon Nov 06 2023(Updated: )
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.
Credit: cve@gitlab.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | >=16.2.0<16.3.6 | |
GitLab | >=16.2.0<16.3.6 | |
GitLab | >=16.4.0<16.4.2 | |
GitLab | >=16.4.0<16.4.2 | |
GitLab | =16.5.0 | |
GitLab | =16.5.0 |
Upgrade to versions 16.5.1, 16.4.2, 16.3.6 or above.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID for this GitLab vulnerability is CVE-2023-5825.
CVE-2023-5825 has a severity of medium (6.5).
This vulnerability affects all versions of GitLab starting from 16.2 before 16.3.6, starting from 16.4 before 16.4.2, and 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 resources.
Yes, a fix is available for CVE-2023-5825. It is recommended to upgrade to GitLab versions 16.3.6, 16.4.2, or 16.5.1.