CVE-2020-13300
First published: Mon Sep 14 2020(Updated: )
GitLab CE/EE version 13.3 prior to 13.3.4 was vulnerable to an OAuth authorization scope change without user consent in the middle of the authorization flow.
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=13.3.0<13.3.4 | |
| GitLab | >=13.3.0<13.3.4 |
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-13300?
CVE-2020-13300 has been classified as a high severity vulnerability.
How do I fix CVE-2020-13300?
To fix CVE-2020-13300, you should update GitLab CE/EE to version 13.3.4 or later.
What is the impact of CVE-2020-13300 on users?
CVE-2020-13300 allows unauthorized changes to OAuth authorization scopes during the user authorization process.
Which versions of GitLab are affected by CVE-2020-13300?
CVE-2020-13300 affects GitLab CE/EE versions from 13.3.0 to 13.3.3.
Is user consent required for OAuth authorization changes in CVE-2020-13300?
CVE-2020-13300 indicates that OAuth authorization scope changes can occur without user consent.
- agent/type
- agent/references
- agent/weakness
- agent/author
- agent/softwarecombine
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/severity
- 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/13.3.0