First published: Thu Sep 12 2024(Updated: )
A server-side request forgery issue has been discovered in GitLab EE affecting all versions starting from 16.8 prior to 17.1.7, from 17.2 prior to 17.2.5, and from 17.3 prior to 17.3.2. It was possible for an attacker to make requests to internal resources using a custom Maven Dependency Proxy URL
Credit: cve@gitlab.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | >=16.8.0<17.1.7 | |
GitLab | >=16.8.0<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 version 17.1.7, 17.2.5 or 17.3.2
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-8635 has a high severity rating due to its potential for exploitation through server-side request forgery.
To fix CVE-2024-8635, upgrade GitLab to version 17.1.7 or later, or 17.2.5 or later, or 17.3.2 or later.
CVE-2024-8635 affects all versions of GitLab starting from 16.8 up to 17.1.6, from 17.2.0 up to 17.2.4, and from 17.3.0 up to 17.3.1.
CVE-2024-8635 is a server-side request forgery (SSRF) vulnerability.
Mitigation strategies for CVE-2024-8635 are limited, and upgrading is the recommended approach to eliminate the vulnerability.