CVE-2020-27831
First published: Wed Dec 09 2020(Updated: )
A flaw was found in Red Hat Quay, where it does not properly protect the authorization token when authorizing email addresses for repository email notifications. This flaw allows an attacker to add email addresses they do not own to repository notifications.
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| redhat/Quay | <3.3.3 | 3.3.3 |
| Redhat Quay | >=3.0.0<3.3.3 |
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 CVE-2020-27831?
CVE-2020-27831 is a vulnerability found in Red Hat Quay where it does not properly protect the authorization token when authorizing email addresses for repository email notifications.
How does CVE-2020-27831 affect Red Hat Quay?
CVE-2020-27831 allows an attacker to add email addresses they do not own to repository notifications in Red Hat Quay.
What is the severity of CVE-2020-27831?
The severity of CVE-2020-27831 is medium with a severity value of 4.3.
How can I fix CVE-2020-27831?
To fix CVE-2020-27831, upgrade Red Hat Quay to version 3.3.3.
Where can I find more information about CVE-2020-27831?
You can find more information about CVE-2020-27831 on the Red Hat Bugzilla, GitHub, and Red Hat Security Advisories websites.
- agent/author
- agent/description
- agent/event
- agent/first-publish-date
- agent/last-modified-date
- agent/references
- agent/severity
- agent/softwarecombine
- agent/tags
- agent/type
- agent/weakness
- collector/nvd-index
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2020-27831
- agent/software-canonical-lookup
- vendor/redhat
- canonical/redhat quay
- version/redhat quay/3.0.0
- package-manager/redhat