CVE-2020-13356: High severity GitLab GitLab vulnerability
An issue has been discovered in GitLab CE/EE affecting all versions starting from 8.8.9. A specially crafted request could bypass Multipart protection and read files in certain specific paths on the server. Affected versions are: >=8.8.9, <13.3.9,>=13.4, <13.4.5,>=13.5, <13.5.2.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
GitLab CE/EEto a version that resolves this vulnerability.Fixed in 13.3.9 - Upgrade
Upgrade
GitLab CE/EEto a version that resolves this vulnerability.Fixed in 13.4.5 - Upgrade
Upgrade
GitLab CE/EEto a version that resolves this vulnerability.Fixed in 13.5.2
Event History
Frequently Asked Questions
What is the severity of CVE-2020-13356?
CVE-2020-13356 has been categorized as a critical vulnerability due to its ability to bypass Multipart protection and expose sensitive files.
How does CVE-2020-13356 affect GitLab installations?
CVE-2020-13356 affects GitLab installations from version 8.8.9 up to version 13.3.9 and various ranges of versions beyond that.
How do I fix CVE-2020-13356?
To fix CVE-2020-13356, you should update GitLab to the latest version recommended by GitLab to mitigate the vulnerability.
What versions of GitLab are impacted by CVE-2020-13356?
CVE-2020-13356 impacts GitLab versions between 8.8.9 and 13.3.9, and also specific ranges in versions 13.4 and 13.5.
Is there a workaround for CVE-2020-13356?
There are no documented workarounds for CVE-2020-13356, so upgrading to a non-vulnerable version is the recommended solution.