Learn about CVE-2021-22187, a medium severity vulnerability in GitLab <13.6.7 allowing jobs to run post-project deletion. Find mitigation steps and affected versions.
An issue has been discovered in GitLab that affects versions before 13.6.7, leading to a potential resource exhaustion problem that allows jobs to run even after the project is deleted.
Understanding CVE-2021-22187
This vulnerability in GitLab has a CVSS base score of 4.3, indicating a medium severity issue.
What is CVE-2021-22187?
CVE-2021-22187 is a vulnerability in GitLab versions prior to 13.6.7 that could result in resource exhaustion, enabling jobs to continue even after a project deletion.
The Impact of CVE-2021-22187
The impact of this vulnerability is considered medium with low attack complexity and vector, affecting availability but not confidentiality or integrity.
Technical Details of CVE-2021-22187
This section provides detailed technical information about CVE-2021-22187.
Vulnerability Description
The vulnerability allows uncontrolled resource consumption in GitLab, potentially leading to jobs persistence after project deletion.
Affected Systems and Versions
GitLab versions <13.6.7, >=13.7 and <13.7.7, >=13.8 and <13.8.4 are affected by this vulnerability.
Exploitation Mechanism
By exploiting this issue, attackers could exhaust resources and maintain job execution even after the related project is deleted.
Mitigation and Prevention
To address CVE-2021-22187, immediate and long-term security measures should be implemented.
Immediate Steps to Take
It is recommended to update GitLab to a version that includes the necessary security patches to mitigate this vulnerability.
Long-Term Security Practices
Enhance monitoring and resource usage controls within GitLab environments to prevent resource exhaustion vulnerabilities.
Patching and Updates
Regularly apply security updates and patches provided by GitLab to address known vulnerabilities and enhance system security.