Filtered by vendor Gitlab
Subscriptions
Total
981 CVE
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2019-13003 | 1 Gitlab | 1 Gitlab | 2020-03-11 | 7.5 High |
| An issue was discovered in GitLab Community and Enterprise Edition before 12.0.3. One of the parsers used by Gilab CI was vulnerable to a resource exhaustion attack. It allows Uncontrolled Resource Consumption. | ||||
| CVE-2019-13007 | 1 Gitlab | 1 Gitlab | 2020-03-10 | 4.9 Medium |
| An issue was discovered in GitLab Community and Enterprise Edition 11.11 through 12.0.2. When an admin enabled one of the service templates, it was triggering an action that leads to resource depletion. It allows Uncontrolled Resource Consumption. | ||||
| CVE-2019-12444 | 1 Gitlab | 1 Gitlab | 2020-03-10 | 6.1 Medium |
| An issue was discovered in GitLab Community and Enterprise Edition 8.9 through 11.11. Wiki Pages contained a lack of input validation which resulted in a persistent XSS vulnerability. | ||||
| CVE-2019-13001 | 1 Gitlab | 1 Gitlab | 2020-03-10 | 4.3 Medium |
| An issue was discovered in GitLab Community and Enterprise Edition 11.9 and later through 12.0.2. GitLab Snippets were vulnerable to an authorization issue that allowed unauthorized users to add comments to a private snippet. It allows authentication bypass. | ||||
| CVE-2019-12445 | 1 Gitlab | 1 Gitlab | 2020-03-10 | 5.4 Medium |
| An issue was discovered in GitLab Community and Enterprise Edition 8.4 through 11.11. A malicious user could execute JavaScript code on notes by importing a specially crafted project file. It allows XSS. | ||||
| CVE-2019-12443 | 1 Gitlab | 1 Gitlab | 2020-03-10 | 9.8 Critical |
| An issue was discovered in GitLab Community and Enterprise Edition 10.2 through 11.11. Multiple features contained Server-Side Request Forgery (SSRF) vulnerabilities caused by an insufficient validation to prevent DNS rebinding attacks. | ||||
| CVE-2019-12442 | 1 Gitlab | 1 Gitlab | 2020-03-10 | 6.1 Medium |
| An issue was discovered in GitLab Enterprise Edition 11.7 through 11.11. The epic details page contained a lack of input validation and output encoding issue which resulted in a persistent XSS vulnerability on child epics. | ||||
| CVE-2019-12441 | 1 Gitlab | 1 Gitlab | 2020-03-10 | 7.5 High |
| An issue was discovered in GitLab Community and Enterprise Edition 8.4 through 11.11. The protected branches feature contained a access control issue which resulted in a bypass of the protected branches restriction rules. It has Incorrect Access Control. | ||||
| CVE-2019-12446 | 1 Gitlab | 1 Gitlab | 2020-03-10 | 7.5 High |
| An issue was discovered in GitLab Community and Enterprise Edition 8.3 through 11.11. It allows Information Exposure through an Error Message. | ||||
| CVE-2019-12432 | 1 Gitlab | 1 Gitlab | 2020-03-10 | 4.3 Medium |
| An issue was discovered in GitLab Community and Enterprise Edition 8.13 through 11.11. Non-member users who subscribed to issue notifications could access the title of confidential issues through the unsubscription page. It allows Information Disclosure. | ||||
| CVE-2019-12433 | 1 Gitlab | 1 Gitlab | 2020-03-10 | 5.3 Medium |
| An issue was discovered in GitLab Community and Enterprise Edition 11.7 through 11.11. It has Improper Input Validation. Restricted visibility settings allow creating internal projects in private groups, leading to multiple permission issues. | ||||
| CVE-2019-12825 | 1 Gitlab | 1 Gitlab | 2020-02-28 | 4.3 Medium |
| Unauthorized Access to the Container Registry of other groups was discovered in GitLab Enterprise 12.0.0-pre. In other words, authenticated remote attackers can read Docker registries of other groups. When a legitimate user changes the path of a group, Docker registries are not adapted, leaving them in the old namespace. They are not protected and are available to all other users with no previous access to the repo. | ||||
| CVE-2020-8114 | 1 Gitlab | 1 Gitlab | 2020-02-07 | 9.8 Critical |
| GitLab EE 8.9 and later through 12.7.2 has Insecure Permission | ||||
| CVE-2020-7979 | 1 Gitlab | 1 Gitlab | 2020-02-07 | 5.3 Medium |
| GitLab EE 8.9 and later through 12.7.2 has Insecure Permission | ||||
| CVE-2020-7966 | 1 Gitlab | 1 Gitlab | 2020-02-07 | 7.5 High |
| GitLab EE 11.11 and later through 12.7.2 allows Directory Traversal. | ||||
| CVE-2020-7971 | 1 Gitlab | 1 Gitlab | 2020-02-06 | 6.1 Medium |
| GitLab EE 11.0 and later through 12.7.2 allows XSS. | ||||
| CVE-2020-7972 | 1 Gitlab | 1 Gitlab | 2020-02-06 | 7.5 High |
| GitLab EE 12.2 has Insecure Permissions (issue 2 of 2). | ||||
| CVE-2020-7967 | 1 Gitlab | 1 Gitlab | 2020-02-06 | 4.3 Medium |
| GitLab EE 8.0 through 12.7.2 has Insecure Permissions (issue 1 of 2). | ||||
| CVE-2020-7973 | 1 Gitlab | 1 Gitlab | 2020-02-06 | 6.1 Medium |
| GitLab through 12.7.2 allows XSS. | ||||
| CVE-2020-7977 | 1 Gitlab | 1 Gitlab | 2020-02-06 | 5.3 Medium |
| GitLab EE 8.8 and later through 12.7.2 has Insecure Permissions. | ||||