CVE-2020-10077: SSRF
First published: Fri Mar 13 2020(Updated: )
GitLab EE 3.0 through 12.8.1 allows SSRF. An internal investigation revealed that a particular deprecated service was creating a server side request forgery risk.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=3.0.0<=12.8.1 |
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-2020-10077?
CVE-2020-10077 is classified as a medium severity vulnerability due to its potential to cause server-side request forgery.
How do I fix CVE-2020-10077?
To mitigate CVE-2020-10077, upgrade to a version of GitLab EE that is higher than 12.8.1.
What versions of GitLab EE are affected by CVE-2020-10077?
CVE-2020-10077 affects GitLab EE versions from 3.0.0 through 12.8.1.
Is there a workaround for CVE-2020-10077?
There is no specific workaround for CVE-2020-10077; upgrading is the recommended action.
What type of vulnerability is CVE-2020-10077?
CVE-2020-10077 is a server-side request forgery (SSRF) vulnerability.
- agent/references
- agent/type
- agent/severity
- agent/weakness
- agent/author
- 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/3.0.0
- version/gitlab/12.8.1