CVE-2022-3726: Critical severity GitLab GitLab vulnerability
Lack of sand-boxing of OpenAPI documents in GitLab CE/EE affecting all versions from 12.6 prior to 15.3.5, 15.4 prior to 15.4.4, and 15.5 prior to 15.5.2 allows an attacker to trick a user to click on the Swagger OpenAPI viewer and issue HTTP requests that affect the victim's account.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
GitLab CE/EEto a version that resolves this vulnerability.Fixed in 15.3.5 - Upgrade
Upgrade
GitLab CE/EEto a version that resolves this vulnerability.Fixed in 15.4.4 - Upgrade
Upgrade
GitLab CE/EEto a version that resolves this vulnerability.Fixed in 15.5.2
Event History
Frequently Asked Questions
What is the severity of CVE-2022-3726?
CVE-2022-3726 has a moderate severity rating, indicating it poses a significant risk under certain conditions.
How do I fix CVE-2022-3726?
To fix CVE-2022-3726, upgrade your GitLab installation to version 15.3.5 or later, or 15.4.4 or later, or 15.5.2 or later.
What versions are affected by CVE-2022-3726?
CVE-2022-3726 affects GitLab CE/EE versions from 12.6 up to, but not including, 15.3.5, 15.4 up to, but not including, 15.4.4, and 15.5 up to, but not including, 15.5.2.
What kind of attack does CVE-2022-3726 allow?
CVE-2022-3726 allows an attacker to trick users into issuing HTTP requests that can manipulate their accounts through the Swagger OpenAPI viewer.
What is the impact of CVE-2022-3726 on GitLab users?
The impact of CVE-2022-3726 on GitLab users can include unauthorized actions performed on their accounts if they interact with malicious OpenAPI documents.