First published: Thu Nov 14 2024(Updated: )
An issue has been discovered in GitLab CE/EE affecting all versions from 17.3 before 17.3.7, 17.4 before 17.4.4, and 17.5 before 17.5.2. Improper output encoding could lead to XSS if CSP is not enabled.
Credit: cve@gitlab.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | >=17.3.0<17.3.7 | |
GitLab | >=17.3.0<17.3.7 | |
GitLab | >=17.4.0<17.4.4 | |
GitLab | >=17.4.0<17.4.4 | |
GitLab | >=17.5.0<17.5.2 | |
GitLab | >=17.5.0<17.5.2 |
Upgrade to versions 17.3.7, 17.4.4, 17.5.2 or above.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-8180 is classified as a moderate severity vulnerability due to the potential for cross-site scripting (XSS) attacks.
To fix CVE-2024-8180, upgrade GitLab to version 17.3.7, 17.4.4, or 17.5.2 or later.
CVE-2024-8180 affects all GitLab CE/EE versions from 17.3.0 before 17.3.7, 17.4.0 before 17.4.4, and 17.5.0 before 17.5.2.
CVE-2024-8180 is an improper output encoding vulnerability that can lead to cross-site scripting (XSS) if content security policy (CSP) is not enabled.
Yes, enabling content security policy (CSP) can help mitigate the risks associated with CVE-2024-8180.