CVE-2022-3820

Public Exploit

Description

An issue has been discovered in GitLab affecting all versions starting from 15.4 prior to 15.4.4, and 15.5 prior to 15.5.2. GitLab was not performing correct authentication with some Package Registries when IP address restrictions were configured, allowing an attacker already in possession of a valid Deploy Token to misuse it from any location.

Category

6.5
CVSS
Severity: Medium
CVSS 3.1 •
EPSS 0.03%
Vendor Advisory gitlab.com Vendor Advisory gitlab.com
Affected: GitLab GitLab
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2022-3820?
CVE-2022-3820 has been scored as a medium severity vulnerability.
How to fix CVE-2022-3820?
To fix CVE-2022-3820, 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-2022-3820 being actively exploited in the wild?
It is possible that CVE-2022-3820 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-2022-3820?
CVE-2022-3820 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.