CVE-2022-0244 Path traversal in GitLab
Attackers can read arbitrary files via group import due to incorrect file handling in GitLab.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2022-0244?
CVE-2022-0244 is a high-severity path traversal vulnerability in Gitlab Gitlab, published on 18 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
An issue has been discovered in GitLab CE/EE affecting all versions starting with 14.5. Arbitrary file read was possible by importing a group was due to incorrect handling of file.
Weakness: CWE-552
Which versions are affected by CVE-2022-0244?
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.3, 14.6.2 |
Products include Gitlab Gitlab.
How do I fix CVE-2022-0244?
Upgrade gitlab to a fixed version for your release line: 14.5.3 or 14.6.2.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2022-0244 being exploited?
There is no known exploitation of CVE-2022-0244 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-0244, GHSA-66vj-p7rx-6jrr, UBUNTU-CVE-2022-0244.