Vulnerabilities > Gitlab
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2021-10-05 | CVE-2021-22262 | Incorrect Authorization vulnerability in Gitlab Missing access control in all GitLab versions starting from 13.12 before 14.0.9, all versions starting from 14.1 before 14.1.4, and all versions starting from 14.2 before 14.2.2 with Jira Cloud integration enabled allows Jira users without administrative privileges to add and remove Jira Connect Namespaces via the GitLab.com for Jira Cloud application configuration page | 4.3 |
| 2021-10-05 | CVE-2021-22264 | Unspecified vulnerability in Gitlab An issue has been discovered in GitLab affecting all versions starting from 13.8 before 14.0.9, all versions starting from 14.1 before 14.1.4, all versions starting from 14.2 before 14.2.2. | 6.5 |
| 2021-10-05 | CVE-2021-39870 | Unspecified vulnerability in Gitlab In all versions of GitLab CE/EE since version 11.11, an instance that has the setting to disable Repo by URL import enabled is bypassed by an attacker making a crafted API call. | 4.3 |
| 2021-10-05 | CVE-2021-39881 | Unspecified vulnerability in Gitlab In all versions of GitLab CE/EE since version 7.7, the application may let a malicious user create an OAuth client application with arbitrary scope names which may allow the malicious user to trick unsuspecting users to authorize the malicious client application using the spoofed scope name and description. | 3.5 |
| 2021-10-05 | CVE-2021-39886 | Incorrect Default Permissions vulnerability in Gitlab Permissions rules were not applied while issues were moved between projects of the same group in GitLab versions starting with 10.6 and up to 14.1.7 allowing users to read confidential Epic references. | 4.3 |
| 2021-10-05 | CVE-2021-39889 | Authorization Bypass Through User-Controlled Key vulnerability in Gitlab In all versions of GitLab EE since version 14.1, due to an insecure direct object reference vulnerability, an endpoint may reveal the protected branch name to a malicious user who makes a crafted API call with the ID of the protected branch. | 4.3 |
| 2021-10-05 | CVE-2021-39891 | Improper Cross-boundary Removal of Sensitive Data vulnerability in Gitlab In all versions of GitLab CE/EE since version 8.0, access tokens created as part of admin's impersonation of a user are not cleared at the end of impersonation which may lead to unnecessary sensitive info disclosure. | 4.9 |
| 2021-10-05 | CVE-2021-39866 | Unspecified vulnerability in Gitlab A business logic error in the project deletion process in GitLab 13.6 and later allows persistent access via project access tokens. | 5.4 |
| 2021-10-05 | CVE-2021-39867 | Server-Side Request Forgery (SSRF) vulnerability in Gitlab In all versions of GitLab CE/EE since version 8.15, a DNS rebinding vulnerability in Gitea Importer may be exploited by an attacker to trigger Server Side Request Forgery (SSRF) attacks. | 8.1 |
| 2021-10-05 | CVE-2021-39869 | Unspecified vulnerability in Gitlab In all versions of GitLab CE/EE since version 8.9, project exports may expose trigger tokens configured on that project. | 6.5 |