CVE-2022-0124 Open redirect in GitLab
Attackers can craft malicious URLs in GitLab's Slack integration to redirect users, requiring the integration to be enabled.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2022-0124?
CVE-2022-0124 is a medium-severity vulnerability in Gitlab Gitlab, published on 18 Jan 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
An issue has been discovered affecting GitLab versions prior to 14.4.5, between 14.5.0 and 14.5.3, and between 14.6.0 and 14.6.1. Gitlab's Slack integration is incorrectly validating user input and allows to craft malicious URLs that are sent to slack.
Weakness: CWE-116
Which versions are affected by CVE-2022-0124?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | All versions | 14.4.5, 14.5.3, 14.6.1 |
Products include Gitlab Gitlab.
How do I fix CVE-2022-0124?
Upgrade gitlab to a fixed version for your release line: 14.4.5, 14.5.3 or 14.6.1.
Is CVE-2022-0124 being exploited?
There is no known exploitation of CVE-2022-0124 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-0124, GHSA-7668-4r26-7chc, UBUNTU-CVE-2022-0124.