CVE-2024-0456

CVE-2024-0456 is a medium-severity vulnerability in Gitlab with a CVSS 3.x base score of 4.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-425.

Key facts

Description

An authorization vulnerability exists in GitLab versions 14.0 prior to 16.6.6, 16.7 prior to 16.7.4, and 16.8 prior to 16.8.1. An unauthorized attacker is able to assign arbitrary users to MRs that they created within the project

Frequently asked questions

What is CVE-2024-0456?
An authorization vulnerability exists in GitLab versions 14.0 prior to 16.6.6, 16.7 prior to 16.7.4, and 16.8 prior to 16.8.1. An unauthorized attacker is able to assign arbitrary users to MRs that they created within the project
How severe is CVE-2024-0456?
CVE-2024-0456 has a CVSS 3.x base score of 4.3, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability none.
Is CVE-2024-0456 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (39th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2024-0456?
CVE-2024-0456 primarily affects Gitlab. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2024-0456?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2024-0456 have an EU (EUVD) identifier?
Yes. CVE-2024-0456 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-16251.
When was CVE-2024-0456 published?
CVE-2024-0456 was published on 2024-01-26 and last updated on 2026-06-17.

References

Affected products (4)

More vulnerabilities in Gitlab

All CVEs affecting Gitlab →

Other CWE-425 vulnerabilities

Browse all CWE-425 vulnerabilities →