First published: Thu Oct 08 2020(Updated: )
An issue has been discovered in GitLab affecting all versions prior to 13.2.10, 13.3.7 and 13.4.2. Sessions keys are stored in plain-text in Redis which allows attacker with Redis access to authenticate as any user that has a session stored in Redis
Credit: cve@gitlab.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | >=10.8.0<13.2.10 | |
GitLab | >=10.8.0<13.2.10 | |
GitLab | >=13.3.0<13.3.7 | |
GitLab | >=13.3.0<13.3.7 | |
GitLab | >=13.4.0<13.4.2 | |
GitLab | >=13.4.0<13.4.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-13344 is considered a medium severity vulnerability due to session keys being stored in plain-text in Redis.
To fix CVE-2020-13344, upgrade GitLab to versions 13.2.10, 13.3.7, or 13.4.2 or later.
CVE-2020-13344 affects all GitLab versions prior to 13.2.10, 13.3.7, and 13.4.2.
An attacker needs access to Redis to exploit CVE-2020-13344 and authenticate as any user with stored sessions.
Yes, CVE-2020-13344 is relevant to both the community and enterprise editions of GitLab.