CVE-2024-6678

GitLab vulnerability

9.9 CRITICALEPSS 1.99%

Published12 Sept 2024

Description

An issue was discovered in GitLab CE/EE affecting all versions starting from 8.14 prior to 17.1.7, starting from 17.2 prior to 17.2.5, and starting from 17.3 prior to 17.3.2, which allows an attacker to trigger a pipeline as an arbitrary user under certain circumstances.

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

GitLab≥ 17.2.0 < 17.2.5 · ≥ 17.3.0 < 17.3.2 · ≥ 8.14.0 < 17.1.7

Remediation

Fixed in

GitLab≥ 17.2.5

Frequently asked

Is CVE-2024-6678 being actively exploited?

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

How severe is CVE-2024-6678?

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

Which products are affected by CVE-2024-6678?

Affected products include GitLab.

How do I fix CVE-2024-6678?

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

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-6678 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.