🛡️ CVE-2022-3286 — gitlab

🟡 CVSS 5.0 — Medium ✅ No Known Exploit CWE-284 OSV
5.0
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

Lack of IP address checking in GitLab EE affecting all versions from 14.2 prior to 15.2.5, 15.3 prior to 15.3.4, and 15.4 prior to 15.4.1 allows a group member to bypass IP restrictions when using a deploy token

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality low, integrity none, availability none.

Weakness class

CVE-2022-3286 is classified as CWE-284: Improper Access Control. The software does not restrict an action to the actors that should be allowed to perform it.

Affected software

CVE-2022-3286 is recorded against 1 package.

  • gitlab

Timeline and source

Published on 6 March 2024 and last revised on 17 June 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

gitlab.com (Web)
gitlab.com (Web)
nvd.nist.gov (Web)

CVE-2022-3286 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity MEDIUM
CVSS Score 5.0
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CWE CWE-284
Public Exploit ✅ No
Source OSV
Published 2024-03-06
Updated 2026-08-12
Modified 2026-06-17
Fix URL N/A

Affected Packages

Software From version Fixed in
gitlab — —

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in gitlab

CVE-2022-3286 is rated CVSS 5.0 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.