Total
1295 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2021-22238 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 3.5 LOW | 6.8 MEDIUM |
|
An issue has been discovered in GitLab affecting all versions starting with 13.3. GitLab was vulnerable to a stored XSS by using the design feature in issues.
|
|||||
| CVE-2021-22237 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 4.0 MEDIUM | 6.6 MEDIUM |
|
Under specialized conditions, GitLab may allow a user with an impersonation token to perform Git actions even if impersonation is disabled. This vulnerability is present in GitLab CE/EE versions before 13.12.9, 14.0.7, 14.1.2
|
|||||
| CVE-2021-22236 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 6.5 MEDIUM | 5.5 MEDIUM |
|
Due to improper handling of OAuth client IDs, new subscriptions generated OAuth tokens on an incorrect OAuth client application. This vulnerability is present in GitLab CE/EE since version 14.1.
|
|||||
| CVE-2021-22234 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 3.5 LOW | 9.6 CRITICAL |
|
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 on the server.
|
|||||
| CVE-2021-22233 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 4.0 MEDIUM | 4.3 MEDIUM |
|
An information disclosure vulnerability in GitLab EE versions 13.10 and later allowed a user to read project details
|
|||||
| CVE-2021-22232 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 3.5 LOW | 3.5 LOW |
|
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-22231 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 4.0 MEDIUM | 3.5 LOW |
|
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-22230 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 6.5 MEDIUM | 4.9 MEDIUM |
|
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-22229 | 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.8. Under a special condition it was possible to access data of an internal repository through project fork done by a project member.
|
|||||
| CVE-2021-22228 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 4.0 MEDIUM | 6.5 MEDIUM |
|
An issue has been discovered in GitLab affecting all versions before 13.11.6, all versions starting from 13.12 before 13.12.6, and all versions starting from 14.0 before 14.0.2. Improper access control allows unauthorised users to access project details using Graphql.
|
|||||
| CVE-2021-22227 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 4.3 MEDIUM | 6.1 MEDIUM |
|
A reflected cross-site script vulnerability in GitLab before versions 13.11.6, 13.12.6 and 14.0.2 allowed an attacker to send a malicious link to a victim and trigger actions on their behalf if they clicked it
|
|||||
| CVE-2021-22226 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 4.9 MEDIUM | 6.5 MEDIUM |
|
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-22225 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 3.5 LOW | 4.7 MEDIUM |
|
Insufficient input sanitization in markdown in GitLab version 13.11 and up allows an attacker to exploit a stored cross-site scripting vulnerability via a specially-crafted markdown
|
|||||
| CVE-2021-22224 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 4.3 MEDIUM | 7.1 HIGH |
|
A cross-site request forgery vulnerability in the GraphQL API in GitLab since version 13.12 and before versions 13.12.6 and 14.0.2 allowed an attacker to call mutations as the victim
|
|||||
| CVE-2021-22223 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 4.3 MEDIUM | 6.1 MEDIUM |
|
Client-Side code injection through Feature Flag name in GitLab CE/EE starting with 11.9 allows a specially crafted feature flag name to PUT requests on behalf of other users via clicking on a link
|
|||||
| CVE-2021-22221 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 6.4 MEDIUM | 6.5 MEDIUM |
|
An issue has been discovered in GitLab affecting all versions starting from 12.9.0 before 13.10.5, all versions starting from 13.11.0 before 13.11.5, all versions starting from 13.12.0 before 13.12.2. Insufficient expired password validation in various operations allow user to maintain limited access after their password expired
|
|||||
| CVE-2021-22220 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 3.5 LOW | 6.1 MEDIUM |
|
An issue has been discovered in GitLab affecting all versions starting with 13.10. GitLab was vulnerable to a stored XSS in blob viewer of notebooks.
|
|||||
| CVE-2021-22219 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 4.0 MEDIUM | 4.4 MEDIUM |
|
All versions of GitLab CE/EE starting from 9.5 before 13.10.5, all versions starting from 13.11 before 13.11.5, and all versions starting from 13.12 before 13.12.2 allow a high privilege user to obtain sensitive information from log files because the sensitive information was not correctly registered for log masking.
|
|||||
| CVE-2021-22218 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 4.0 MEDIUM | 2.6 LOW |
|
All versions of GitLab CE/EE starting from 12.8 before 13.10.5, all versions starting from 13.11 before 13.11.5, and all versions starting from 13.12 before 13.12.2 were affected by an issue in the handling of x509 certificates that could be used to spoof author of signed commits.
|
|||||
| CVE-2021-22217 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 4.0 MEDIUM | 6.5 MEDIUM |
|
A denial of service vulnerability in all versions of GitLab CE/EE before 13.12.2, 13.11.5 or 13.10.5 allows an attacker to cause uncontrolled resource consumption with a specially crafted issue or merge request
|
|||||
| CVE-2021-22216 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 4.0 MEDIUM | 6.5 MEDIUM |
|
A denial of service vulnerability in all versions of GitLab CE/EE before 13.12.2, 13.11.5 or 13.10.5 allows an attacker to cause uncontrolled resource consumption with a very long issue or merge request description
|
|||||
| CVE-2021-22215 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 4.0 MEDIUM | 7.5 HIGH |
|
An information disclosure vulnerability in GitLab EE versions 13.11 and later allowed a project owner to leak information about the members' on-call rotations in other projects
|
|||||
| CVE-2021-22214 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 4.3 MEDIUM | 6.8 MEDIUM |
|
When requests to the internal network for webhooks are enabled, a server-side request forgery vulnerability in GitLab CE/EE affecting all versions starting from 10.5 was possible to exploit for an unauthenticated attacker even on a GitLab instance where registration is limited
|
|||||
| CVE-2021-22213 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 4.3 MEDIUM | 8.8 HIGH |
|
A cross-site leak vulnerability in the OAuth flow of all versions of GitLab CE/EE since 7.10 allowed an attacker to leak an OAuth access token by getting the victim to visit a malicious page with Safari
|
|||||
| CVE-2021-22211 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 3.5 LOW | 3.1 LOW |
|
An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.7. GitLab Dependency Proxy, under certain circumstances, can impersonate a user resulting in possibly incorrect access handling.
|
|||||
| CVE-2021-22210 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 5.0 MEDIUM | 5.3 MEDIUM |
|
An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.2. When querying the repository branches through API, GitLab was ignoring a query parameter and returning a considerable amount of results.
|
|||||
| CVE-2021-22209 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 5.0 MEDIUM | 7.5 HIGH |
|
An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.8. GitLab was not properly validating authorisation tokens which resulted in GraphQL mutation being executed.
|
|||||
| CVE-2021-22208 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 4.0 MEDIUM | 4.3 MEDIUM |
|
An issue has been discovered in GitLab affecting versions starting with 13.5 up to 13.9.7. Improper permission check could allow the change of timestamp for issue creation or update.
|
|||||
| 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-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.
|
|||||