First published: Wed Nov 18 2020(Updated: )
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.
Credit: cve@gitlab.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | >=8.8.9<13.3.9 | |
GitLab | >=8.8.9<13.3.9 | |
GitLab | >=13.4.0<13.4.5 | |
GitLab | >=13.4.0<13.4.5 | |
GitLab | >=13.5.0<13.5.2 | |
GitLab | >=13.5.0<13.5.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-13356 has been categorized as a critical vulnerability due to its ability to bypass Multipart protection and expose sensitive files.
CVE-2020-13356 affects GitLab installations from version 8.8.9 up to version 13.3.9 and various ranges of versions beyond that.
To fix CVE-2020-13356, you should update GitLab to the latest version recommended by GitLab to mitigate the vulnerability.
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.
There are no documented workarounds for CVE-2020-13356, so upgrading to a non-vulnerable version is the recommended solution.