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.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Quay | Redhat | 3.0.0 (including) | 3.3.3 (excluding) |
| Red Hat Quay 3 | RedHat | quay/quay-container-security-rhel8-operator:v3.3.3-2 | * |
| Red Hat Quay 3 | RedHat | quay/quay-container-security-rhel8-operator-metadata:v3.3.3-4 | * |
| Red Hat Quay 3 | RedHat | quay/quay-openshift-bridge-rhel8-operator:v3.3.3-1 | * |
| Red Hat Quay 3 | RedHat | quay/quay-openshift-bridge-rhel8-operator-metadata:v3.3.2-2 | * |
| Red Hat Quay 3 | RedHat | quay/quay-operator-bundle:v3.3.3-3 | * |
| Red Hat Quay 3 | RedHat | quay/quay-rhel8-operator:v3.3.3-3 | * |
Access control involves the use of several protection mechanisms such as:
When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses: