CVE-2024-6446: Business Logic Errors in GitLab
An issue has been discovered in GitLab affecting all versions starting from 17.1 to 17.1.7, 17.2 prior to 17.2.5 and 17.3 prior to 17.3.2. A crafted URL could be used to trick a victim to trust an attacker controlled application.
Other sources
An issue has been discovered in GitLab CE/EE affecting all versions starting from 17.1 to 17.1.7, 17.2 prior to 17.2.5 and 17.3 prior to 17.3.2. A crafted URL could be used to trick a victim to trust an attacker controlled application. This is a low severity issue (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N, 3.5). It is now mitigated in the latest release and is assigned CVE-2024-6446.
— GitLab
Affected Software
Remediation
Information
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
What is the severity of CVE-2024-6446?
CVE-2024-6446 has been rated as a medium severity vulnerability affecting multiple versions of GitLab.
How do I fix CVE-2024-6446?
To fix CVE-2024-6446, upgrade to GitLab versions 17.1.8, 17.2.5, or 17.3.2 or later.
What versions of GitLab are affected by CVE-2024-6446?
CVE-2024-6446 affects GitLab versions 17.1.0 to 17.1.7, 17.2.0 to 17.2.5, and 17.3.0 to 17.3.2.
Is CVE-2024-6446 remotely exploitable?
Yes, CVE-2024-6446 can be exploited remotely via a crafted URL that tricks the user into trusting an attacker-controlled application.
What impact does CVE-2024-6446 have on GitLab users?
CVE-2024-6446 can potentially expose users to phishing attacks and unauthorized trust in malicious applications.