CVE-2020-13353
First published: Tue Nov 17 2020(Updated: )
When importing repos via URL, one time use git credentials were persisted beyond the expected time window in Gitaly 1.79.0 or above.
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=1.79.0<13.3.9 | |
| GitLab | >=13.4.0<13.4.5 | |
| GitLab | >=13.5.0<13.5.2 |
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-13353?
CVE-2020-13353 is considered a medium severity vulnerability due to its potential exposure of sensitive git credentials.
How do I fix CVE-2020-13353?
To fix CVE-2020-13353, users should update Gitaly to a version above 13.5.2, 13.4.5, or 13.3.9.
What versions are affected by CVE-2020-13353?
CVE-2020-13353 affects Gitaly versions from 1.79.0 to 13.5.2, including 13.4.0 to 13.4.5, and 13.3.9.
What type of credentials does CVE-2020-13353 impact?
CVE-2020-13353 impacts one-time use git credentials that are incorrectly persisted beyond their intended lifecycle.
Who is affected by CVE-2020-13353?
Anyone using Gitaly versions within the specified ranges is at risk of having their git credentials inappropriately retained.
- agent/references
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/last-modified-date
- agent/severity
- agent/author
- agent/description
- agent/event
- agent/first-publish-date
- agent/source
- agent/tags
- agent/softwarecombine
- collector/nvd-index
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/gitlab
- canonical/gitlab
- version/gitlab/1.79.0
- version/gitlab/13.4.0
- version/gitlab/13.5.0