First published: Fri Jun 11 2021(Updated: )
When requests to the internal network for webhooks are enabled, a server-side request forgery vulnerability in GitLab affecting all versions starting from 10.5 was possible to exploit for an unauthenticated attacker even on a GitLab instance where registration is disabled
Credit: cve@gitlab.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | >=10.5.0<13.6.7 | |
GitLab | >=10.5.0<13.6.7 | |
GitLab | >=13.7.0<13.7.7 | |
GitLab | >=13.7.0<13.7.7 | |
GitLab | >=13.8.0<13.8.4 | |
GitLab | >=13.8.0<13.8.4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2021-22175 is classified as a high severity vulnerability due to its potential for server-side request forgery by unauthenticated attackers.
To fix CVE-2021-22175, upgrade GitLab to version 13.8.4 or later.
CVE-2021-22175 affects GitLab versions from 10.5.0 up to and including 13.8.3.
Yes, CVE-2021-22175 can be exploited by unauthenticated attackers even if registration is disabled on the GitLab instance.
CVE-2021-22175 is a server-side request forgery (SSRF) vulnerability.