CVE-2024-8647 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in GitLab

Medium 5.4 Published Updated

Attackers can leak anti-CSRF tokens to external sites via path traversal when Harbor integration is enabled on self-hosted GitLab instances.

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-2024-8647?

CVE-2024-8647 is a medium-severity path traversal vulnerability in Gitlab Gitlab, published on 12 Dec 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

Official description

An issue was discovered in GitLab affecting all versions starting 15.2 to 17.4.6, 17.5 prior to 17.5.4, and 17.6 prior to 17.6.2. On self hosted installs, it was possible to leak the anti-CSRF-token to an external site while the Harbor integration was enabled.

Weakness: CWE-22

Which versions are affected by CVE-2024-8647?

1 open source package ship an affected version, including gitlab. It affects 1 product.

PackageAffectedFixed in
gitlab BitnamiFrom 15.2.017.4.6, 17.5.4, 17.6.2

Products include Gitlab Gitlab.

How do I fix CVE-2024-8647?

Upgrade gitlab to a fixed version for your release line: 17.4.6, 17.5.4 or 17.6.2.

Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.

Is CVE-2024-8647 being exploited?

There is no known exploitation of CVE-2024-8647 in the wild and no public exploit code.

All Gitlab Gitlab vulnerabilities

Sources

Also known as BIT-gitlab-2024-8647, GHSA-4xpw-245v-vp2w, UBUNTU-CVE-2024-8647.

Is CVE-2024-8647 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free