Developer Tools

In GitLab versions 17.1 to 17.1.7, 17.2 prior to 17.2.5, and 17.3 prior to 17.3.2 a medium severity vulnerability CVE-2024-6446 was detected. This vulnerability allows attackers to create a fake link that could trick someone into trusting a harmful app controlled by the attacker. To fix this issue, users should upgrade GitLab to versions 17.2.5, 17.3.2, or later. For more details, visit https://nvd.nist.gov/vuln/detail/CVE-2024-6446.

In GitLab CE/EE versions from 15.10 before 17.1.7, from 17.2 before 17.2.5, from 17.3 before 17.3.2 a medium severity vulnerability CVE-2024-5435 was detected. This vulnerability in GitLab EE/CE could expose user passwords from repository mirror configurations. To fix this problem, users should upgrade to version 17.3.2, 17.2.5, or 17.1.7. For more details, visit https://nvd.nist.gov/vuln/detail/CVE-2024-5435.

In GitLab CE/EE versions 17.0 before 17.1.7, 17.2 before 17.2.5, and 17.3 before 17.3.2, a medium severity vulnerability CVE-2024-6389 was detected. This vulnerability allows attackers with guest user access to view commit information through the release Atom endpoint, bypassing proper permission checks. To address this issue, it is recommended to update to versions 17.1.7, 17.2.5, or 17.3.2. For more details, visit https://avd.aquasec.com/nvd/2024/cve-2024-6389.

In GitLab EE versions from 17.2 prior to 17.2.5, 17.3 prior to 17.3.2 a medium severity vulnerability CVE-2024-8311 was detected. This vulnerability allows authenticated users to bypass variable overwrite protection in GitLab EE pipelines using a CI/CD template. To fix this problem, users should upgrade to version 17.2.5, 17.3.2 or later. For more details, visit https://nvd.nist.gov/vuln/detail/CVE-2024-8311.

In GitLab CE/EE versions 16.4 to 17.3.2 a high severity vulnerability CVE-2024-8124 was detected. This vulnerability in GitLab CE/EE could cause a Denial of Service through a specific POST request. To fix this problem, users should upgrade to version 17.3.2 or later. For more details, visit https://nvd.nist.gov/vuln/detail/CVE-2024-8124.

In GitLab CE/EE versions starting from 16.7 prior to 17.1.7, 17.2 prior to 17.2.5, and 17.3 prior to 17.3.2 a low severity vulnerability CVE-2024-6685 was detected. This vulnerability allows unauthorized attackers to gain access to sensitive group runner information. To fix this problem, users should upgrade GitLab to version 17.1.7, 17.2.5, 17.3.2, or later. For additional details, visit https://nvd.nist.gov/vuln/detail/CVE-2024-6685.

In GitLab CE/EE versions from 13.7 prior to 17.1.7, from 17.2 prior to 17.2.5, and from 17.3 prior to 17.3.2 a medium severity vulnerability CVE-2024-8641 was detected. This vulnerability allows attackers with a victim’s CI_JOB_TOKEN to obtain a GitLab session token belonging to the victim. To fix this issue users should upgrade GitLab CE/EE to version 17.1.7, 17.2.5, or 17.3.2 For more details, visit https://avd.aquasec.com/nvd/2024/cve-2024-8641.

In GitLab versions from 16.9.7 to before 17.1.7, 17.2 to before 17.2.5, and 17.3 to before 17.3.2 a medium severity vulnerability CVE-2024-8754 was detected. This vulnerability allows attackers to squat on accounts by linking arbitrary unclaimed provider identities when JWT authentication is configured. To address this issue, update to GitLab version 17.1.7 or later, 17.2.5 or later, or 17.3.2 or later. For more details, visit https://avd.aquasec.com/nvd/2024/cve-2024-8754.

In GitLab versions from 16.11 to before 17.1.7, from 17.2 to before 17.2.5, and from 17.3 to before 17.3.2 a high severity vulnerability CVE-2024-8640 was detected. This vulnerability allows attackers to inject commands into a connected Cube server due to incomplete input filtering. To address this issue, update to GitLab version 17.1.7, 17.2.5, or 17.3.2 or later. For more details, visit https://avd.aquasec.com/nvd/2024/cve-2024-8640.