Medium severity · published May 27, 2021
CVE-2020-27831
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
4.3
CVSS
0.5%
EPSS
No
On KEV
Description
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.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Confidentiality
None
Integrity
Low
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.5% · higher than 46% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
QU
Quay · Redhat
3.0.0 before 3.3.3 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2020-27831
CVE.org
https://www.cve.org/CVERecord?id=CVE-2020-27831
Issue Tracking
https://bugzilla.redhat.com/show_bug.cgi?id=1905758
More from Quay
9.8
CVE-2021-3762
A directory traversal vulnerability was found in the ClairCore engine of Clair
9.0
CVE-2020-27832
A flaw was found in Red Hat Quay, where it has a persistent Cross-site Scripting (XSS) vulnerability when displaying a repository's notification
8.8
CVE-2026-32590
Mirror-registry: remote code execution using pickle deserialization
8.8
CVE-2022-1227
A privilege escalation flaw was found in Podman
8.8
CVE-2019-3864
A vulnerability was discovered in all quay-2 versions before quay-3.0.0, in the Quay web GUI where POST requests include a specific parameter which is used as a CSRF token