Filtered by vendor Gitlab
Subscribe
Total
1094 CVE
CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
---|---|---|---|---|---|
CVE-2021-22206 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 4.0 MEDIUM | 6.8 MEDIUM |
An issue has been discovered in GitLab affecting all versions starting from 11.6. Pull mirror credentials are exposed that allows other maintainers to be able to view the credentials in plain-text, | |||||
CVE-2021-22203 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 7.5 HIGH | 7.5 HIGH |
An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.7.9 before 13.8.7, all versions starting from 13.9 before 13.9.5, and all versions starting from 13.10 before 13.10.1. A specially crafted Wiki page allowed attackers to read arbitrary files on the server. | |||||
CVE-2021-22202 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 4.3 MEDIUM | 2.4 LOW |
An issue has been discovered in GitLab CE/EE affecting all previous versions. If the victim is an admin, it was possible to issue a CSRF in System hooks through the API. | |||||
CVE-2021-22201 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 4.0 MEDIUM | 9.6 CRITICAL |
An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.9. A specially crafted import file could read files on the server. | |||||
CVE-2021-22200 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 4.3 MEDIUM | 5.9 MEDIUM |
An issue has been discovered in GitLab CE/EE affecting all versions starting with 12.6. Under a special condition it was possible to access data of an internal repository through a public project fork as an anonymous user. | |||||
CVE-2021-22199 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 3.5 LOW | 3.5 LOW |
An issue has been discovered in GitLab affecting all versions starting with 12.9. GitLab was vulnerable to a stored XSS if scoped labels were used. | |||||
CVE-2021-22198 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 4.0 MEDIUM | 4.3 MEDIUM |
An issue has been discovered in GitLab CE/EE affecting all versions from 13.8 and above allowing an authenticated user to delete incident metric images of public projects. | |||||
CVE-2021-22197 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 4.0 MEDIUM | 3.5 LOW |
An issue has been discovered in GitLab CE/EE affecting all versions starting from 10.6 where an infinite loop exist when an authenticated user with specific rights access a MR having source and target branch pointing to each other | |||||
CVE-2021-22196 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 3.5 LOW | 6.3 MEDIUM |
An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.4. It was possible to exploit a stored cross-site-scripting in merge request via a specifically crafted branch name. | |||||
CVE-2021-22195 | 1 Gitlab | 1 Gitlab-vscode-extension | 2024-11-21 | 6.8 MEDIUM | 8.6 HIGH |
Client side code execution in gitlab-vscode-extension v3.15.0 and earlier allows attacker to execute code on user system | |||||
CVE-2021-22194 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 2.1 LOW | 5.7 MEDIUM |
In all versions of GitLab, marshalled session keys were being stored in Redis. | |||||
CVE-2021-22193 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 3.5 LOW | 3.5 LOW |
An issue has been discovered in GitLab affecting all versions starting with 7.1. A member of a private group was able to validate the use of a specific name for private project. | |||||
CVE-2021-22192 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 6.5 MEDIUM | 9.9 CRITICAL |
An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.2 allowing unauthorized authenticated users to execute arbitrary code on the server. | |||||
CVE-2021-22190 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 4.0 MEDIUM | 8.5 HIGH |
A path traversal vulnerability via the GitLab Workhorse in all versions of GitLab could result in the leakage of a JWT token | |||||
CVE-2021-22189 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 6.5 MEDIUM | 5.9 MEDIUM |
Starting with version 13.7 the Gitlab CE/EE editions were affected by a security issue related to the validation of the certificates for the Fortinet OTP that could result in authentication issues. | |||||
CVE-2021-22188 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 5.0 MEDIUM | 5.3 MEDIUM |
An issue has been discovered in GitLab affecting all versions starting with 13.0. Confidential issue titles in Gitlab were readable by an unauthorised user via branch logs. | |||||
CVE-2021-22187 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 4.0 MEDIUM | 4.3 MEDIUM |
An issue has been discovered in GitLab affecting all versions of Gitlab EE/CE before 13.6.7. A potential resource exhaustion issue that allowed running or pending jobs to continue even after project was deleted. | |||||
CVE-2021-22186 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 4.0 MEDIUM | 4.9 MEDIUM |
An authorization issue in GitLab CE/EE version 9.4 and up allowed a group maintainer to modify group CI/CD variables which should be restricted to group owners | |||||
CVE-2021-22185 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 3.5 LOW | 5.4 MEDIUM |
Insufficient input sanitization in wikis in GitLab version 13.8 and up allows an attacker to exploit a stored cross-site scripting vulnerability via a specially-crafted commit to a wiki | |||||
CVE-2021-22184 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 2.1 LOW | 6.2 MEDIUM |
An information disclosure issue in GitLab starting from version 12.8 allowed a user with access to the server logs to see sensitive information that wasn't properly redacted. |