CVE-2024-0402

GitLab vulnerability

9.9 CRITICALEPSS 3.78%

Published26 Jan 2024

Description

An issue has been discovered in GitLab CE/EE affecting all versions from 16.0 prior to 16.6.6, 16.7 prior to 16.7.4, and 16.8 prior to 16.8.1 which allows an authenticated user to write files to arbitrary locations on the GitLab server while creating a workspace.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredLow

User interactionNone

ScopeChanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Affected products

GitLab16.8.0 · ≥ 16.0.0 < 16.5.8 · ≥ 16.6.0 < 16.6.6 · ≥ 16.7.0 < 16.7.4

Remediation

Fixed in

GitLab≥ 16.5.8

Frequently asked

Is CVE-2024-0402 being actively exploited?

CVE-2024-0402 is not in the CISA KEV catalog. Its EPSS exploit probability is 3.78%.

How severe is CVE-2024-0402?

CVE-2024-0402 has a CVSS 3.1 base score of 9.9, rated critical. EPSS estimates a 3.78% probability of exploitation.

Which products are affected by CVE-2024-0402?

Affected products include GitLab.

How do I fix CVE-2024-0402?

Upgrade affected software to a fixed version, for example GitLab 16.5.8 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-0402 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.