CVE-2024-9164

GitLab vulnerability

9.6 CRITICALEPSS 1.04%

Published11 Oct 2024

Description

An issue was discovered in GitLab EE affecting all versions starting from 12.5 prior to 17.2.9, starting from 17.3, prior to 17.3.5, and starting from 17.4 prior to 17.4.2, which allows running pipelines on arbitrary branches.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredLow

User interactionNone

ScopeChanged

ConfidentialityHigh

IntegrityHigh

AvailabilityNone

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

Affected products

GitLab≥ 12.5.0 < 17.2.9 · ≥ 17.3.0 < 17.3.5 · ≥ 17.4.0 < 17.4.2

Remediation

Fixed in

GitLab≥ 17.2.9

Frequently asked

Is CVE-2024-9164 being actively exploited?

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

How severe is CVE-2024-9164?

CVE-2024-9164 has a CVSS 3.1 base score of 9.6, rated critical. EPSS estimates a 1.04% probability of exploitation.

Which products are affected by CVE-2024-9164?

Affected products include GitLab.

How do I fix CVE-2024-9164?

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

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-9164 against the real software inventory on every managed device, every day. 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.