30 matches found
CVE-2021-39869
In all versions of GitLab CE/EE since version 8.9, project exports may expose trigger tokens configured on that project...
Code injection
In all versions of GitLab CE/EE since version 8.9, project exports may expose trigger tokens configured on that project...
UBUNTU-CVE-2021-39869
In all versions of GitLab CE/EE since version 8.9, project exports may expose trigger tokens configured on that project...
CVE-2021-39869
In all versions of GitLab CE/EE since version 8.9, project exports may expose trigger tokens configured on that project...
CVE-2021-39869
In all versions of GitLab CE/EE since version 8.9, project exports may expose trigger tokens configured on that project...
CVE-2021-39869
In all versions of GitLab CE/EE since version 8.9, project exports may expose trigger tokens configured on that project...
CVE-2021-39869
In GitLab CE/EE, CVE-2021-39869 affects all versions since 8.9 and allows project exports to expose trigger tokens configured on a project. The connected sources confirm this exception to normal export behavior and describe the impact as token exposure, without detailing exploit methods or specif...
CVE-2021-39869
Removed by vendor...
PT-2021-22716 · Gitlab · Gitlab Ce/Ee +1
Name of the Vulnerable Software and Affected Versions: GitLab CE/EE versions 8.9 and later Description: The issue concerns project exports in GitLab CE/EE, where trigger tokens configured on a project may be exposed. This affects all versions since 8.9. Recommendations: For GitLab CE/EE versions...
GitLab: Users can download old project exports due to unclaimed namespace
TL;DR: Happy new year and happy birthday, @douwem! Vulnerability details When a user renames its namespace, another user can claim the namespace and download old export files from the victim. The attack scenario here is that someone would scrape existing GitLab namespaces users and groups, which...