First published: Thu Nov 04 2021(Updated: )
In all versions of GitLab CE/EE since version 13.0, a privileged user, through an API call, can change the visibility level of a group or a project to a restricted option even after the instance administrator sets that visibility option as restricted in settings.
Credit: cve@gitlab.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | >=13.0.0<14.2.6 | |
GitLab | >=13.0.0<14.2.6 | |
GitLab | >=14.3.0<14.3.4 | |
GitLab | >=14.3.0<14.3.4 | |
GitLab | =14.4.0 | |
GitLab | =14.4.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2021-39903 is considered a high severity vulnerability due to its potential to change project visibility settings by privileged users.
To mitigate CVE-2021-39903, upgrade GitLab to version 14.4.0 or later, or apply any available patches.
CVE-2021-39903 affects all GitLab CE/EE versions from 13.0.0 up to but not including 14.2.6 as well as specific versions between 14.3.0 and 14.3.4.
GitLab provides the ability for instance administrators to restrict visibility settings, but this vulnerability allows privileged users to bypass those restrictions.
Privileged users on GitLab instances configured with restricted project visibility are directly impacted by CVE-2021-39903.