CVE-2018-17450: SSRF
First published: Sat Apr 15 2023(Updated: )
An issue was discovered in GitLab Community and Enterprise Edition before 11.1.7, 11.2.x before 11.2.4, and 11.3.x before 11.3.1. There is Server-Side Request Forgery (SSRF) via the Kubernetes integration, leading (for example) to disclosure of a GCP service token.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | <11.1.7 | |
| GitLab | <11.1.7 | |
| GitLab | >=11.2.0<11.2.4 | |
| GitLab | >=11.2.0<11.2.4 | |
| GitLab | =11.3.0 | |
| GitLab | =11.3.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2018-17450?
CVE-2018-17450 has been classified as a medium severity vulnerability.
How do I fix CVE-2018-17450?
To fix CVE-2018-17450, upgrade GitLab to version 11.1.7, 11.2.4, or 11.3.1 or later.
What type of vulnerability is CVE-2018-17450?
CVE-2018-17450 is identified as a Server-Side Request Forgery (SSRF) vulnerability.
What can be compromised due to CVE-2018-17450?
Due to CVE-2018-17450, there is potential disclosure of a Google Cloud Platform (GCP) service token.
Which versions of GitLab are affected by CVE-2018-17450?
GitLab Community and Enterprise Editions before 11.1.7, between 11.2.0 and 11.2.4, and 11.3.0 are affected by CVE-2018-17450.
- agent/references
- agent/type
- agent/weakness
- agent/author
- agent/severity
- agent/softwarecombine
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/gitlab
- canonical/gitlab
- version/gitlab/11.2.0
- version/gitlab/11.3.0