CVE-2022-0427 Cross-site request forgery in GitLab
Attackers can perform arbitrary HTTP POST requests on users' behalf via unsanitized Jupyter notebook attributes, potentially leading to account takeover.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2022-0427?
CVE-2022-0427 is a high-severity vulnerability in Gitlab Gitlab, published on 28 Mar 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official description
Missing sanitization of HTML attributes in Jupyter notebooks in all versions of GitLab CE/EE since version 14.5 allows an attacker to perform arbitrary HTTP POST requests on a user's behalf leading to potential account takeover
Weakness: CWE-352
Which versions are affected by CVE-2022-0427?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 14.5.0 | 14.5.4, 14.6.4, 14.7.1 |
Products include Gitlab Gitlab.
How do I fix CVE-2022-0427?
Upgrade gitlab to a fixed version for your release line: 14.5.4, 14.6.4 or 14.7.1.
Is CVE-2022-0427 being exploited?
There is no known exploitation of CVE-2022-0427 in the wild and no public exploit code.
Other vulnerabilities in Gitlab Gitlab
- CVE-2026-97229 GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound
- CVE-2026-85706 GitLab Community Edition and Enterprise Edition Path Traversal
- CVE-2023-7028 GitLab Community and Enterprise Editions Improper Access Control
- CVE-2021-22205 GitLab Community and Enterprise Editions Remote Code Execution
- CVE-2021-39935 GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF)
Sources
Also known as BIT-gitlab-2022-0427, GHSA-2xwq-3g46-4j22, UBUNTU-CVE-2022-0427.