CVE-2024-1211: CSRF
First published: Fri Jan 31 2025(Updated: )
An issue has been discovered in GitLab CE/EE affecting all versions starting from 10.6 prior to 16.9.7, starting from 16.10 prior to 16.10.5, and starting from 16.11 prior to 16.11.2 in which cross-site request forgery may have been possible on GitLab instances configured to use JWT as an OmniAuth provider.
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=10.6<16.9.7>=16.10<16.10.5>=16.11<16.11.2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2024-1211?
CVE-2024-1211 is considered a high-severity vulnerability due to its potential for cross-site request forgery.
How do I fix CVE-2024-1211?
To fix CVE-2024-1211, update GitLab CE/EE to version 16.9.7 or later, 16.10.5 or later, or 16.11.2 or later.
What versions of GitLab are affected by CVE-2024-1211?
CVE-2024-1211 affects GitLab CE/EE versions starting from 10.6 up to but not including 16.9.7, 16.10 prior to 16.10.5, and 16.11 prior to 16.11.2.
Can CVE-2024-1211 be exploited remotely?
Yes, CVE-2024-1211 can potentially be exploited remotely if the affected GitLab instances are configured to use JWT as an OmniAuth provider.
What is the nature of the vulnerability in CVE-2024-1211?
CVE-2024-1211 is a cross-site request forgery vulnerability that may allow attackers to perform unauthorized actions on behalf of a user.
- collector/nvd-api
- source/NVD
- agent/type
- agent/description
- agent/first-publish-date
- agent/last-modified-date
- agent/severity
- agent/weakness
- agent/source
- agent/references
- agent/author
- agent/event
- agent/softwarecombine
- agent/tags
- agent/guess-ai
- agent/software-canonical-lookup
- vendor/gitlab
- canonical/gitlab