CE/EE
by GitLab Inc.
Source repositories
CVEs (414)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2021-22243 | 0.00 | — | 0.00 | Aug 25, 2021 | Under specialized conditions, GitLab CE/EE versions starting 7.10 may allow existing GitLab users to use an invite URL meant for another email address to gain access into a group. | |||
| CVE-2021-22244 | 0.00 | — | 0.00 | Aug 25, 2021 | Improper authorization in the vulnerability report feature in GitLab EE affecting all versions since 13.1 allowed a reporter to access vulnerability data | |||
| CVE-2021-22247 | 0.00 | — | 0.00 | Aug 25, 2021 | Improper authorization in GitLab CE/EE affecting all versions since 13.0 allows guests in private projects to view CI/CD analytics | |||
| CVE-2021-22245 | 0.00 | — | 0.00 | Aug 25, 2021 | Improper validation of commit author in GitLab CE/EE affecting all versions allowed an attacker to make several pages in a project impossible to view | |||
| CVE-2021-22256 | 0.00 | — | 0.00 | Aug 25, 2021 | Improper authorization in GitLab CE/EE affecting all versions since 12.6 allowed guest users to create issues for Sentry errors and track their status | |||
| CVE-2021-22250 | 0.00 | — | 0.00 | Aug 25, 2021 | Improper authorization in GitLab CE/EE affecting all versions since 13.3 allowed users to view and delete impersonation tokens that administrators created for their account | |||
| CVE-2021-22249 | 0.00 | — | 0.00 | Aug 23, 2021 | A verbose error message in GitLab EE affecting all versions since 12.2 could disclose the private email address of a user invited to a group | |||
| CVE-2021-22248 | 0.00 | — | 0.00 | Aug 23, 2021 | Improper authorization on the pipelines page in GitLab CE/EE affecting all versions since 13.12 allowed unauthorized users to view some pipeline information for public projects that have access to pipelines restricted to members only | |||
| CVE-2021-22251 | 0.00 | — | 0.00 | Aug 23, 2021 | Improper validation of invited users' email address in GitLab EE affecting all versions since 12.2 allowed projects to add members with email address domain that should be blocked by group settings | |||
| CVE-2021-22252 | 0.00 | — | 0.00 | Aug 23, 2021 | A confusion between tag and branch names in GitLab CE/EE affecting all versions since 13.7 allowed a Developer to access protected CI variables which should only be accessible to Maintainers | |||
| CVE-2021-22253 | 0.00 | — | 0.00 | Aug 23, 2021 | Improper authorization in GitLab EE affecting all versions since 13.4 allowed a user who previously had the necessary access to trigger deployments to protected environments under specific conditions after the access has been removed | |||
| CVE-2021-22254 | 0.00 | — | 0.00 | Aug 20, 2021 | Under very specific conditions a user could be impersonated using Gitlab shell. This vulnerability affects GitLab CE/EE 13.1 and later through 14.1.2, 14.0.7 and 13.12.9. | |||
| CVE-2021-22234 | 0.00 | — | 0.00 | Aug 5, 2021 | An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.11 before 13.11.7, all versions starting from 13.12 before 13.12.8, and all versions starting from 14.0 before 14.0.4. A specially crafted design image allowed attackers to read arbitrary files… | |||
| CVE-2021-22241 | 0.00 | — | 0.00 | Aug 5, 2021 | An issue has been discovered in GitLab CE/EE affecting all versions starting from 14.0. It was possible to exploit a stored cross-site-scripting via a specifically crafted default branch name. | |||
| CVE-2021-22240 | 0.00 | — | 0.00 | Aug 5, 2021 | Improper access control in GitLab EE versions 13.11.6, 13.12.6, and 14.0.2 allows users to be created via single sign on despite user cap being enabled | |||
| CVE-2021-22233 | 0.00 | — | 0.00 | Jul 7, 2021 | An information disclosure vulnerability in GitLab EE versions 13.10 and later allowed a user to read project details | |||
| CVE-2021-22230 | 0.00 | — | 0.00 | Jul 7, 2021 | Improper code rendering while rendering merge requests could be exploited to submit malicious code. This vulnerability affects GitLab CE/EE 9.3 and later through 13.11.6, 13.12.6, and 14.0.2. | |||
| CVE-2021-22231 | 0.00 | — | 0.00 | Jul 7, 2021 | A denial of service in user's profile page is found starting with GitLab CE/EE 8.0 that allows attacker to reject access to their profile page via using a specially crafted username. | |||
| CVE-2021-22226 | 0.00 | — | 0.00 | Jul 6, 2021 | Under certain conditions, some users were able to push to protected branches that were restricted to deploy keys in GitLab CE/EE since version 13.9 | |||
| CVE-2021-22232 | 0.00 | — | 0.00 | Jul 6, 2021 | HTML injection was possible via the full name field before versions 13.11.6, 13.12.6, and 14.0.2 in GitLab CE |
- CVE-2021-22243Aug 25, 2021risk 0.00cvss —epss 0.00
Under specialized conditions, GitLab CE/EE versions starting 7.10 may allow existing GitLab users to use an invite URL meant for another email address to gain access into a group.
- CVE-2021-22244Aug 25, 2021risk 0.00cvss —epss 0.00
Improper authorization in the vulnerability report feature in GitLab EE affecting all versions since 13.1 allowed a reporter to access vulnerability data
- CVE-2021-22247Aug 25, 2021risk 0.00cvss —epss 0.00
Improper authorization in GitLab CE/EE affecting all versions since 13.0 allows guests in private projects to view CI/CD analytics
- CVE-2021-22245Aug 25, 2021risk 0.00cvss —epss 0.00
Improper validation of commit author in GitLab CE/EE affecting all versions allowed an attacker to make several pages in a project impossible to view
- CVE-2021-22256Aug 25, 2021risk 0.00cvss —epss 0.00
Improper authorization in GitLab CE/EE affecting all versions since 12.6 allowed guest users to create issues for Sentry errors and track their status
- CVE-2021-22250Aug 25, 2021risk 0.00cvss —epss 0.00
Improper authorization in GitLab CE/EE affecting all versions since 13.3 allowed users to view and delete impersonation tokens that administrators created for their account
- CVE-2021-22249Aug 23, 2021risk 0.00cvss —epss 0.00
A verbose error message in GitLab EE affecting all versions since 12.2 could disclose the private email address of a user invited to a group
- CVE-2021-22248Aug 23, 2021risk 0.00cvss —epss 0.00
Improper authorization on the pipelines page in GitLab CE/EE affecting all versions since 13.12 allowed unauthorized users to view some pipeline information for public projects that have access to pipelines restricted to members only
- CVE-2021-22251Aug 23, 2021risk 0.00cvss —epss 0.00
Improper validation of invited users' email address in GitLab EE affecting all versions since 12.2 allowed projects to add members with email address domain that should be blocked by group settings
- CVE-2021-22252Aug 23, 2021risk 0.00cvss —epss 0.00
A confusion between tag and branch names in GitLab CE/EE affecting all versions since 13.7 allowed a Developer to access protected CI variables which should only be accessible to Maintainers
- CVE-2021-22253Aug 23, 2021risk 0.00cvss —epss 0.00
Improper authorization in GitLab EE affecting all versions since 13.4 allowed a user who previously had the necessary access to trigger deployments to protected environments under specific conditions after the access has been removed
- CVE-2021-22254Aug 20, 2021risk 0.00cvss —epss 0.00
Under very specific conditions a user could be impersonated using Gitlab shell. This vulnerability affects GitLab CE/EE 13.1 and later through 14.1.2, 14.0.7 and 13.12.9.
- CVE-2021-22234Aug 5, 2021risk 0.00cvss —epss 0.00
An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.11 before 13.11.7, all versions starting from 13.12 before 13.12.8, and all versions starting from 14.0 before 14.0.4. A specially crafted design image allowed attackers to read arbitrary files…
- CVE-2021-22241Aug 5, 2021risk 0.00cvss —epss 0.00
An issue has been discovered in GitLab CE/EE affecting all versions starting from 14.0. It was possible to exploit a stored cross-site-scripting via a specifically crafted default branch name.
- CVE-2021-22240Aug 5, 2021risk 0.00cvss —epss 0.00
Improper access control in GitLab EE versions 13.11.6, 13.12.6, and 14.0.2 allows users to be created via single sign on despite user cap being enabled
- CVE-2021-22233Jul 7, 2021risk 0.00cvss —epss 0.00
An information disclosure vulnerability in GitLab EE versions 13.10 and later allowed a user to read project details
- CVE-2021-22230Jul 7, 2021risk 0.00cvss —epss 0.00
Improper code rendering while rendering merge requests could be exploited to submit malicious code. This vulnerability affects GitLab CE/EE 9.3 and later through 13.11.6, 13.12.6, and 14.0.2.
- CVE-2021-22231Jul 7, 2021risk 0.00cvss —epss 0.00
A denial of service in user's profile page is found starting with GitLab CE/EE 8.0 that allows attacker to reject access to their profile page via using a specially crafted username.
- CVE-2021-22226Jul 6, 2021risk 0.00cvss —epss 0.00
Under certain conditions, some users were able to push to protected branches that were restricted to deploy keys in GitLab CE/EE since version 13.9
- CVE-2021-22232Jul 6, 2021risk 0.00cvss —epss 0.00
HTML injection was possible via the full name field before versions 13.11.6, 13.12.6, and 14.0.2 in GitLab CE
Page 15 of 21