9766 matches found
BIT-GITLAB-2020-13349
An issue has been discovered in GitLab EE affecting all versions starting from 8.12. A regular expression related to a file path resulted in the Advanced Search feature susceptible to catastrophic backtracking. Affected versions are =8.12, =13.4, =13.5, 13.5.2...
BIT-GITLAB-2020-13350
CSRF in runner administration page in all versions of GitLab CE/EE allows an attacker who's able to target GitLab instance administrators to pause/resume runners. Affected versions are =13.5.0, =13.4.0, 13.4.5,13.3.9...
BIT-GITLAB-2020-13351
Insufficient permission checks in scheduled pipeline API in GitLab CE/EE 13.0+ allows an attacker to read variable names and values for scheduled pipelines on projects visible to the attacker. Affected versions are =13.0, =13.4.0, =13.5.0, 13.5.2...
BIT-GITLAB-2020-13352
Private group info is leaked leaked in GitLab CE/EE version 10.2 and above, when the project is moved from private to public group. Affected versions are: =10.2, =13.4, =13.5, 13.5.2...
BIT-GITLAB-2020-13354
A potential DOS vulnerability was discovered in GitLab CE/EE starting with version 12.6. The container registry name check could cause exponential number of backtracks for certain user supplied values resulting in high CPU usage. Affected versions are: =12.6, 13.3.9...
BIT-GITLAB-2020-13355
An issue has been discovered in GitLab CE/EE affecting all versions starting from 8.14. A path traversal is found in LFS Upload that allows attacker to overwrite certain specific paths on the server. Affected versions are: =8.14, =13.4, =13.5, 13.5.2...
BIT-GITLAB-2020-13356
An issue has been discovered in GitLab CE/EE affecting all versions starting from 8.8.9. A specially crafted request could bypass Multipart protection and read files in certain specific paths on the server. Affected versions are: =8.8.9, =13.4, =13.5, 13.5.2...
BIT-GITLAB-2020-13357
An issue was discovered in Gitlab CE/EE versions = 13.1 to = 13.5 to = 13.6 to 13.6.2 allowed an unauthorized user to access the user list corresponding to a feature flag in a project...
BIT-GITLAB-2020-13358
A vulnerability in the internal Kubernetes agent api in GitLab CE/EE version 13.3 and above allows unauthorized access to private projects. Affected versions are: =13.4, =13.3, =13.5, 13.5.2...
BIT-GITLAB-2020-13359
The Terraform API in GitLab CE/EE 12.10+ exposed the object storage signed URL on the delete operation allowing a malicious project maintainer to overwrite the Terraform state, bypassing audit and other business controls. Affected versions are =12.10, =13.4, =13.5, 13.5.2...
BIT-GITLAB-2020-14155
libpcre in PCRE before 8.44 allows an integer overflow via a large number after a ?C substring...
BIT-GITLAB-2020-15525
GitLab EE 11.3 through 13.1.2 has Incorrect Access Control because of the Maven package upload endpoint...
BIT-GITLAB-2020-26405
Path traversal vulnerability in package upload functionality in GitLab CE/EE starting from 12.8 allows an attacker to save packages in arbitrary locations. Affected versions are =12.8, =13.4, =13.5, 13.5.2...
BIT-GITLAB-2020-26406
Certain SAST CiConfiguration information could be viewed by unauthorized users in GitLab EE starting with 13.3. This information was exposed through GraphQL to non-members of public projects with repository visibility restricted as well as guest members on private projects. Affected versions are:...
BIT-GITLAB-2020-26407
A XSS vulnerability exists in Gitlab CE/EE from 12.4 before 13.4.7, 13.5 before 13.5.5, and 13.6 before 13.6.2 that allows an attacker to perform cross-site scripting to other users via importing a malicious project...
BIT-GITLAB-2020-26408
A limited information disclosure vulnerability exists in Gitlab CE/EE from = 12.2 to =13.5 to =13.6 to 13.6.2 that allows an attacker to view limited information in user's private profile...
BIT-GITLAB-2020-26409
A DOS vulnerability exists in Gitlab CE/EE =10.3, =13.5, =13.6, 13.6.2 that allows an attacker to trigger uncontrolled resource by bypassing input validation in markdown fields...
BIT-GITLAB-2020-26411
A potential DOS vulnerability was discovered in all versions of Gitlab starting from 13.4.x =13.4 to =13.5 to =13.6 to 13.6.2. Using a specific query name for a project search can cause statement timeouts that can lead to a potential DOS if abused...
BIT-GITLAB-2020-26412
Removed group members were able to use the To-Do functionality to retrieve updated information on confidential epics starting in GitLab EE 13.2 before 13.6.2...
BIT-GITLAB-2020-26413
An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.4 before 13.6.2. Information disclosure via GraphQL results in user email being unexpectedly visible...
BIT-GITLAB-2020-26414
An issue has been discovered in GitLab affecting all versions starting from 12.4. The regex used for package names is written in a way that makes execution time have quadratic growth based on the length of the malicious input string...
BIT-GITLAB-2020-26415
Information about the starred projects for private user profiles was exposed via the GraphQL API starting from 12.2 via the REST API. This affects GitLab =12.2 to =13.5 to =13.6 to 13.6.2...
BIT-GITLAB-2020-26416
Information disclosure in Advanced Search component of GitLab EE starting from 8.4 results in exposure of search terms via Rails logs. This affects versions =8.4 to =13.5 to =13.6 to 13.6.2...
BIT-GITLAB-2020-26417
Information disclosure via GraphQL in GitLab CE/EE 13.1 and later exposes private group and project membership. This affects versions =13.6 to =13.5 to =13.1 to 13.4.7...
BIT-GITLAB-2020-5197
An issue was discovered in GitLab Community Edition CE and Enterprise Edition EE 5.1 through 12.6.1. It has Incorrect Access Control...
BIT-GITLAB-2020-6832
An issue was discovered in GitLab Enterprise Edition EE 8.9.0 through 12.6.1. Using the project import feature, it was possible for someone to obtain issues from private projects...
BIT-GITLAB-2020-6833
An issue was discovered in GitLab EE 11.3 and later. A GitLab Workhorse bypass could lead to package and file disclosure via request smuggling...
BIT-GITLAB-2020-7966
GitLab EE 11.11 and later through 12.7.2 allows Directory Traversal...
BIT-GITLAB-2020-7967
GitLab EE 8.0 through 12.7.2 has Insecure Permissions issue 1 of 2...
BIT-GITLAB-2020-7968
GitLab EE 8.0 through 12.7.2 has Incorrect Access Control...
BIT-GITLAB-2020-7969
GitLab EE 8.0 and later through 12.7.2 allows Information Disclosure...
BIT-GITLAB-2020-7971
GitLab EE 11.0 and later through 12.7.2 allows XSS...
BIT-GITLAB-2020-7972
GitLab EE 12.2 has Insecure Permissions issue 2 of 2...
BIT-GITLAB-2020-7973
GitLab through 12.7.2 allows XSS...
BIT-GITLAB-2020-7974
GitLab EE 10.1 through 12.7.2 allows Information Disclosure...
BIT-GITLAB-2020-7976
GitLab EE 12.4 and later through 12.7.2 has Incorrect Access Control...
BIT-GITLAB-2020-7977
GitLab EE 8.8 and later through 12.7.2 has Insecure Permissions...
BIT-TENSORFLOW-2020-15190 Segfault in Tensorflow
In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the tf.rawops.Switch operation takes as input a tensor and a boolean and outputs two tensors. Depending on the boolean value, one of the tensors is exactly the input tensor whereas the other one should be an empty tensor. Howeve...
BIT-TENSORFLOW-2020-15191 Undefined behavior in Tensorflow
In Tensorflow before versions 2.2.1 and 2.3.1, if a user passes an invalid argument to dlpack.todlpack the expected validations will cause variables to bind to nullptr while setting a status variable to the error condition. However, this status argument is not properly checked. Hence, code...
BIT-GITLAB-2020-7978
GitLab EE 12.6 and later through 12.7.2 allows Denial of Service...
BIT-TENSORFLOW-2020-15192 Memory leak in Tensorflow
In Tensorflow before versions 2.2.1 and 2.3.1, if a user passes a list of strings to dlpack.todlpack there is a memory leak following an expected validation failure. The issue occurs because the status argument during validation failures is not properly checked. Since each of the above methods ca...
BIT-GITLAB-2020-7979
GitLab EE 8.9 and later through 12.7.2 has Insecure Permission...
BIT-TENSORFLOW-2020-15193 Memory corruption in Tensorflow
In Tensorflow before versions 2.2.1 and 2.3.1, the implementation of dlpack.todlpack can be made to use uninitialized memory resulting in further memory corruption. This is because the pybind11 glue code assumes that the argument is a tensor. However, there is nothing stopping users from passing ...
BIT-GITLAB-2020-8113
GitLab 10.7 and later through 12.7.2 has Incorrect Access Control...
BIT-TENSORFLOW-2020-15194 Denial of Service in Tensorflow
In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the SparseFillEmptyRowsGrad implementation has incomplete validation of the shapes of its arguments. Although reverseindexmapt and gradvaluest are accessed in a similar pattern, only reverseindexmapt is validated to be of proper...
BIT-GITLAB-2020-8114
GitLab EE 8.9 and later through 12.7.2 has Insecure Permission...
BIT-TENSORFLOW-2020-15195 Heap buffer overflow in Tensorflow
In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the implementation of SparseFillEmptyRowsGrad uses a double indexing pattern. It is possible for reverseindexmapi to be an index outside of bounds of gradvalues, thus resulting in a heap buffer overflow. The issue is patched in...
BIT-GITLAB-2020-8795
In GitLab Enterprise Edition EE 12.5.0 through 12.7.5, sharing a group with a group could grant project access to unauthorized users...
BIT-TENSORFLOW-2020-15196 Heap buffer overflow in Tensorflow
In Tensorflow version 2.3.0, the SparseCountSparseOutput and RaggedCountSparseOutput implementations don't validate that the weights tensor has the same shape as the data. The check exists for DenseCountSparseOutput, where both tensors are fully specified. In the sparse and ragged count weights a...