First published: Wed Nov 09 2022(Updated: )
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.
Credit: cve@gitlab.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | >=12.6.0<15.3.5 | |
GitLab | >=12.6.0<15.3.5 | |
GitLab | >=15.4.0<15.4.4 | |
GitLab | >=15.4.0<15.4.4 | |
GitLab | >=15.5.0<15.5.2 | |
GitLab | >=15.5.0<15.5.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-3726 has a moderate severity rating, indicating it poses a significant risk under certain conditions.
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.
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.
CVE-2022-3726 allows an attacker to trick users into issuing HTTP requests that can manipulate their accounts through the Swagger OpenAPI viewer.
The impact of CVE-2022-3726 on GitLab users can include unauthorized actions performed on their accounts if they interact with malicious OpenAPI documents.