CVE-2021-22190 : What You Need to Know

A path traversal vulnerability via the GitLab Workhorse in all versions of GitLab could result in the leakage of a JWT token.

Understanding CVE-2021-22190

This CVE identifies a path traversal vulnerability in GitLab that could lead to the exposure of sensitive JWT tokens.

What is CVE-2021-22190?

A path traversal vulnerability in GitLab's Workhorse component could allow an attacker to access and leak JWT tokens, risking the confidentiality and integrity of sensitive data.

The Impact of CVE-2021-22190

With a CVSS base score of 8.5 (High), this vulnerability poses a significant risk to affected systems. Attackers can exploit this flaw to compromise data confidentiality, integrity, and availability, potentially leading to unauthorized access and data leaks.

Technical Details of CVE-2021-22190

The technical details of this CVE include the following:

Vulnerability Description

Improper handling of URL encoding (hex encoding) in GitLab's Workhorse component, leading to a path traversal vulnerability.

Affected Systems and Versions

Product: GitLab
Vendor: GitLab
Affected Versions:
GitLab >=13.7, <13.7.8
GitLab >=13.8, <13.8.5
GitLab >=13.9, <13.9.2

Exploitation Mechanism

The vulnerability allows an attacker to manipulate URLs to traverse directories and access sensitive JWT tokens used for authentication within GitLab.

Mitigation and Prevention

To address CVE-2021-22190, the following steps are recommended:

Immediate Steps to Take

Update GitLab to a non-vulnerable version immediately.
Monitor for any unauthorized access or abnormal activities.

Long-Term Security Practices

Regularly apply security patches and updates to GitLab.
Conduct security assessments and audits to identify and mitigate similar vulnerabilities.

Patching and Updates

Stay informed about security advisories from GitLab and promptly apply recommended patches and updates to secure your GitLab installation.