CVE-2021-22170

Public Exploit

Description

Assuming a database breach, nonce reuse issues in GitLab 11.6+ allows an attacker to decrypt some of the database's encrypted content

Category

6.2
CVSS
Severity: Medium
CVSS 3.1 •
CVSS 2.0 •
EPSS 0.05%
Third-Party Advisory gitlab.com Third-Party Advisory gitlab.com
Affected: GitLab GitLab
Published at:
Updated at:

References

Link Tags
https://gitlab.com/gitlab-org/gitlab/-/issues/36855 issue tracking exploit third party advisory
https://gitlab.com/gitlab-org/cves/-/blob/master/2021/CVE-2021-22170.json third party advisory exploit

Frequently Asked Questions

What is the severity of CVE-2021-22170?
CVE-2021-22170 has been scored as a medium severity vulnerability.
How to fix CVE-2021-22170?
To fix CVE-2021-22170, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2021-22170 being actively exploited in the wild?
It is possible that CVE-2021-22170 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2021-22170?
CVE-2021-22170 affects GitLab GitLab.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.