CVE-2020-13276
First published: Fri Jun 19 2020(Updated: )
User is allowed to set an email as a notification email even without verifying the new email in all previous GitLab CE/EE versions through 13.0.1
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | <12.9.8 | |
| GitLab | <12.9.8 | |
| GitLab | >=12.10.0<12.10.7 | |
| GitLab | >=12.10.0<12.10.7 | |
| GitLab | =13.0.0 | |
| GitLab | =13.0.0 |
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-13276?
CVE-2020-13276 is classified as a high severity vulnerability due to the potential for unauthorized email notifications.
How do I fix CVE-2020-13276?
To mitigate CVE-2020-13276, upgrade to GitLab version 12.10.8 or later, or 13.0.1 or later.
What versions are affected by CVE-2020-13276?
CVE-2020-13276 affects GitLab versions prior to 12.10.8 and 13.0.1.
What does CVE-2020-13276 exploit?
CVE-2020-13276 exploits the ability for users to set notification emails without email verification.
Is there a workaround for CVE-2020-13276?
There is no official workaround for CVE-2020-13276; upgrading to a secure version is the recommended action.
- agent/references
- agent/weakness
- agent/author
- agent/softwarecombine
- agent/description
- agent/type
- 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/12.10.0
- version/gitlab/13.0.0