Package access bypass via missing IP enforcement
Published Jan 24, 2023 · Updated Apr 2, 2025
Access control bypass in GitLab 15.4.0 through 15.4.5, 15.5.0 through 15.5.4, and 15.6.0 allows remote authenticated users to pull blocked packages. Package-specific project and group policies granted read_package without checking the group IP-violation condition enforced by the parent policy. Exploitation requires a valid Deploy Token and configured group IP restrictions; it exposes packages to token holders outside the allowed network.
Summary
What happened
Access control bypass in GitLab 15.4.0 through 15.4.5, 15.5.0 through 15.5.4, and 15.6.0 allows remote authenticated users to pull blocked packages. Package-specific project and group policies granted read_package without checking the group IP-violation condition enforced by the parent policy. Exploitation requires a valid Deploy Token and configured group IP restrictions; it exposes packages to token holders outside the allowed network.
The record
- CVE
- CVE-2022-3820
- Published
- Jan 24, 2023
- Updated
- Apr 2, 2025
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-290, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 24, 2023CVE publishedPublication date reported by the CVE source.
- Apr 2, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>=15.4, <15.4.6
- Affected versionversion=>=15.5, <15.5.5
- Affected versionversion=>=15.6, <15.6.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- GitLab package-registry IP enforcement regression reportproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo