PT-2024-7210 · Gitlab · Gitlab Ce/Ee+1

CVE-2024-9623 · Published 2024-08-10 · Updated 2025-01-27

Positive Technologies (AI Summary)

CVSS v2.0

6.8

Medium

Base vector

AV:N/AC:L/Au:S/C:N/I:C/A:N

Name of the Vulnerable Software and Affected Versions GitLab CE/EE versions 8.16 through 17.2.9 GitLab CE/EE versions 17.3 through 17.3.5 GitLab CE/EE versions 17.4 through 17.4.2

Description An issue was discovered in GitLab CE/EE, which allows deploy keys to push to an archived repository. The issue is related to authorization procedure flaws, potentially allowing a remote attacker to elevate privileges using deploy keys.

Recommendations For GitLab CE/EE versions 8.16 through 17.2.9, update to version 17.2.9 or later. For GitLab CE/EE versions 17.3 through 17.3.5, update to version 17.3.5 or later. For GitLab CE/EE versions 17.4 through 17.4.2, update to version 17.4.2 or later. As a temporary workaround, consider restricting the use of deploy keys to minimize the risk of exploitation.

Exploit

Fix

Incorrect Authorization

Missing Authorization

Improper Authorization

Weakness Enumeration

CWE-863

CWE-862

CWE-285

Related Identifiers

BDU:2024-08549

BIT-GITLAB-2024-9623

CVE-2024-9623

Affected Products

Gitlab

Gitlab Ce/Ee

References · 16

• 🔥 https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/9xxx/CVE-2024-9623.json · Exploit
• https://ubuntu.com/security/CVE-2024-9623 · Vendor Advisory
• https://nvd.nist.gov/vuln/detail/CVE-2024-9623 · Security Note
• https://osv.dev/vulnerability/CVE-2024-9623 · Vendor Advisory
• https://osv.dev/vulnerability/UBUNTU-CVE-2024-9623 · Vendor Advisory
• https://cve.org/CVERecord?id=CVE-2024-9623 · Security Note
• https://osv.dev/vulnerability/BIT-gitlab-2024-9623 · Vendor Advisory
• https://bdu.fstec.ru/vul/2024-08549 · Security Note
• https://about.gitlab.com/releases/2024/10/09/patch-release-gitlab-17-4-2-released · Note
• https://vuldb.com/?id.279971 · Note
• https://t.me/cvenotify/98333 · Telegram Post
• https://t.me/true_secator/6305 · Telegram Post
• https://twitter.com/CVEnew/status/1844311825099137195 · Twitter Post
• https://twitter.com/oktsec/status/1844386954948882842 · Twitter Post
• https://t.me/cvedetector/7577 · Telegram Post