First published: Thu Sep 12 2024(Updated: )
An issue has been discovered in GitLab EE/CE affecting all versions from 16.9.7 prior to 17.1.7, 17.2 prior to 17.2.5, and 17.3 prior to 17.3.2. An improper input validation error allows attacker to squat on accounts via linking arbitrary unclaimed provider identities when JWT authentication is configured.
Credit: cve@gitlab.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | >=16.9.7<17.1.7 | |
GitLab | >=16.9.7<17.1.7 | |
GitLab | >=17.2.0<17.2.5 | |
GitLab | >=17.2.0<17.2.5 | |
GitLab | >=17.3.0<17.3.2 | |
GitLab | >=17.3.0<17.3.2 |
Upgrade to versions 17.3.2, 17.2.5, 17.1.7 or above.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-8754 is considered a critical vulnerability due to its potential for unauthorized account access.
To fix CVE-2024-8754, upgrade GitLab to version 17.1.7 or later, 17.2.5 or later, or 17.3.2 or later.
CVE-2024-8754 affects both GitLab Community Edition and GitLab Enterprise Edition across multiple affected versions.
CVE-2024-8754 exploits an improper input validation issue that allows attackers to link arbitrary unclaimed provider identities.
CVE-2024-8754 was discovered affecting all versions of GitLab from 16.9.7 prior to 17.1.7, along with specific 17.2 and 17.3 series versions.