Filtered by vendor Gitlab
Subscriptions
Total
1086 CVE
CVE | Vendors | Products | Updated | CVSS v3.1 |
---|---|---|---|---|
CVE-2021-39901 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 2.7 Low |
In all versions of GitLab CE/EE since version 11.10, an admin of a group can see the SCIM token of that group by visiting a specific endpoint. | ||||
CVE-2021-39900 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 2 Low |
Information disclosure from SendEntry in GitLab starting with 10.8 allowed exposure of full URL of artifacts stored in object-storage with a temporary availability via Rails logs. | ||||
CVE-2021-39899 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 2.9 Low |
In all versions of GitLab CE/EE, an attacker with physical access to a user’s machine may brute force the user’s password via the change password function. There is a rate limit in place, but the attack may still be conducted by stealing the session id from the physical compromise of the account and splitting the attack over several IP addresses and passing in the compromised session value from these various locations. | ||||
CVE-2021-39898 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 3.7 Low |
In all versions of GitLab CE/EE since version 10.6, a project export leaks the external webhook token value which may allow access to the project which it was exported from. | ||||
CVE-2021-39897 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 2.6 Low |
Improper access control in GitLab CE/EE version 10.5 and above allowed subgroup members with inherited access to a project from a parent group to still have access even after the subgroup is transferred | ||||
CVE-2021-39896 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 3.8 Low |
In all versions of GitLab CE/EE since version 8.0, when an admin uses the impersonate feature twice and stops impersonating, the admin may be logged in as the second user they impersonated, which may lead to repudiation issues. | ||||
CVE-2021-39895 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 6 Medium |
In all versions of GitLab CE/EE since version 8.0, an attacker can set the pipeline schedules to be active in a project export so when an unsuspecting owner imports that project, pipelines are active by default on that project. Under specialized conditions, this may lead to information disclosure if the project is imported from an untrusted source. | ||||
CVE-2021-39894 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 5.4 Medium |
In all versions of GitLab CE/EE since version 8.0, a DNS rebinding vulnerability exists in Fogbugz importer which may be used by attackers to exploit Server Side Request Forgery attacks. | ||||
CVE-2021-39893 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 5.3 Medium |
A potential DOS vulnerability was discovered in GitLab starting with version 9.1 that allowed parsing files without authorisation. | ||||
CVE-2021-39892 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 4.3 Medium |
In all versions of GitLab CE/EE since version 12.0, a lower privileged user can import users from projects that they don't have a maintainer role on and disclose email addresses of those users. | ||||
CVE-2021-39891 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 5.9 Medium |
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. | ||||
CVE-2021-39890 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 3.1 Low |
It was possible to bypass 2FA for LDAP users and access some specific pages with Basic Authentication in GitLab 14.1.1 and above. | ||||
CVE-2021-39889 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 4.3 Medium |
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. | ||||
CVE-2021-39888 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 4.3 Medium |
In all versions of GitLab EE starting from 13.10 before 14.1.7, all versions starting from 14.2 before 14.2.5, and all versions starting from 14.3 before 14.3.1 a specific API endpoint may reveal details about a private group and other sensitive info inside issue and merge request templates. | ||||
CVE-2021-39887 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 7.3 High |
A stored Cross-Site Scripting vulnerability in the GitLab Flavored Markdown in GitLab CE/EE version 8.4 and above allowed an attacker to execute arbitrary JavaScript code on the victim's behalf. | ||||
CVE-2021-39886 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 2.6 Low |
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. | ||||
CVE-2021-39885 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 8.7 High |
A Stored XSS in merge request creation page in all versions of Gitlab EE starting from 13.7 before 14.1.7, all versions starting from 14.2 before 14.2.5, and all versions starting from 14.3 before 14.3.1 allows an attacker to execute arbitrary JavaScript code on the victim's behalf via malicious approval rule names | ||||
CVE-2021-39884 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 4.3 Medium |
In all versions of GitLab EE since version 8.13, an endpoint discloses names of private groups that have access to a project to low privileged users that are part of that project. | ||||
CVE-2021-39883 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 4.3 Medium |
Improper authorization checks in all versions of GitLab EE starting from 13.11 before 14.1.7, all versions starting from 14.2 before 14.2.5, and all versions starting from 14.3 before 14.3.1 allows subgroup members to see epics from all parent subgroups. | ||||
CVE-2021-39882 | 1 Gitlab | 1 Gitlab | 2024-11-21 | 5.3 Medium |
In all versions of GitLab CE/EE, provided a user ID, anonymous users can use a few endpoints to retrieve information about any GitLab user. |