First published: Thu Nov 04 2021(Updated: )
In all versions of GitLab CE/EE since version 8.0, an attacker can set the pipeline schedules to be active in a project export so when an unsuspecting owner imports that project, pipelines are active by default on that project. Under specialized conditions, this may lead to information disclosure if the project is imported from an untrusted source.
Credit: cve@gitlab.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | >=8.0.0<14.1.7 | |
GitLab | >=8.0.0<14.1.7 | |
GitLab | >=14.2.0<14.2.5 | |
GitLab | >=14.2.0<14.2.5 | |
GitLab | =14.3.0 | |
GitLab | =14.3.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2021-39895 has been classified as a medium severity vulnerability.
To mitigate CVE-2021-39895, update to GitLab version 14.2.5 or later.
CVE-2021-39895 affects all versions of GitLab CE/EE since version 8.0 up to 14.1.7 and certain versions in the 14.2.x and 14.3.x series.
The risks associated with CVE-2021-39895 include the potential for information disclosure when pipeline schedules are inadvertently activated during a project import.
CVE-2021-39895 is considered a local vulnerability as it involves actions taken within the platform itself during project imports.