First published: Thu May 09 2024(Updated: )
An issue has been discovered in GitLab EE affecting all versions from 16.7 before 16.9.7, all versions starting from 16.10 before 16.10.5, all versions starting from 16.11 before 16.11.2. An attacker could force a user with an active SAML session to approve an MR via CSRF.
Credit: cve@gitlab.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | >=16.7.0<16.9.7 | |
GitLab | >=16.7.0<16.9.7 | |
GitLab | >=16.10.0<16.10.5 | |
GitLab | >=16.10.0<16.10.5 | |
GitLab | >=16.11.0<16.11.2 | |
GitLab | >=16.11.0<16.11.2 |
Upgrade to versions 16.9.7, 16.10.5, 16.11.2 or above.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-4597 is considered a medium severity vulnerability due to the potential for CSRF exploitation leading to unauthorized actions.
To fix CVE-2024-4597, upgrade your GitLab instance to version 16.9.7, 16.10.5, or 16.11.2 or later.
CVE-2024-4597 allows attackers to exploit an active SAML session to force users to approve merge requests through CSRF.
CVE-2024-4597 affects GitLab EE versions from 16.7 before 16.9.7, 16.10 from 16.10.0 before 16.10.5, and 16.11 from 16.11.0 before 16.11.2.
While upgrading is the best solution, you can mitigate CVE-2024-4597 risk by monitoring and controlling user sessions and implementing CSRF protection in your applications.