First published: Tue Nov 26 2024(Updated: )
An issue was discovered in GitLab CE/EE affecting all versions from 16.9.8 before 17.4.5, 17.5 before 17.5.3, and 17.6 before 17.6.1. Certain API endpoints could potentially allow unauthorized access to sensitive data due to overly broad application of token scopes.
Credit: cve@gitlab.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | >=16.9.8<17.4.5 | |
GitLab | >=16.9.8<17.4.5 | |
GitLab | >=17.5.0<17.5.3 | |
GitLab | >=17.5.0<17.5.3 | |
GitLab | =17.6.0 | |
GitLab | =17.6.0 |
Upgrade to versions 17.4.5, 17.5.3, 17.6.1 or above.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-11669 is classified as a high severity vulnerability due to its potential for unauthorized access to sensitive data.
To fix CVE-2024-11669, update your GitLab installation to version 17.4.5 or later for versions 16.9.8 through 17.4.5, 17.5.3 or later for versions 17.5.0 through 17.5.3, and 17.6.1 or later for version 17.6.0.
CVE-2024-11669 affects GitLab CE/EE versions from 16.9.8 before 17.4.5, 17.5 before 17.5.3, and 17.6 before 17.6.1.
CVE-2024-11669 is an authorization issue that may lead to unauthorized access to sensitive data.
Users of GitLab CE/EE in the specified affected versions are impacted by CVE-2024-11669.