First published: Thu Oct 10 2024(Updated: )
An issue was discovered in GitLab CE/EE affecting all versions starting from 8.16 prior to 17.2.9, starting from 17.3 prior to 17.3.5, and starting from 17.4 prior to 17.4.2, which allows deploy keys to push to an archived repository.
Credit: cve@gitlab.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | >=8.16.0<17.2.9 | |
GitLab | >=8.16.0<17.2.9 | |
GitLab | >=17.3.0<17.3.5 | |
GitLab | >=17.3.0<17.3.5 | |
GitLab | >=17.4.0<17.4.2 | |
GitLab | >=17.4.0<17.4.2 |
Upgrade to versions 17.2.9, 17.3.5, 17.4.2 or above.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-9623 is considered a high severity vulnerability due to the potential unauthorized access to archived repositories.
To fix CVE-2024-9623, update GitLab to versions 17.2.9, 17.3.5, or 17.4.2 or later.
CVE-2024-9623 affects all GitLab CE/EE versions from 8.16 to before 17.2.9, from 17.3 to before 17.3.5, and from 17.4 to before 17.4.2.
The impact of CVE-2024-9623 allows deploy keys to push changes to archived repositories, which could lead to unauthorized data alterations.
CVE-2024-9623 affects users of GitLab CE/EE who are running vulnerable versions as specified in the advisory.