SecOraLens
CriticalCVE

Critical Red Hat Quay Flaw Lets Attackers Read and Overwrite All Private Container Images in a Registry

The Hacker News·Source published ·1 min read

What happened?

A critical flaw in Red Hat Quay allows an attacker who can access a Quay registry to read and overwrite private container images in every repository. Quay enables anonymous access by default, and while it is enabled, the attacker needs no account. When it is off, anyone with a valid account can still exploit the flaw, Red Hat said yesterday.

Key details

  • A critical flaw in Red Hat Quay lets an attacker with registry access read and overwrite private container images in every repository.
  • Quay enables anonymous access by default, so no account is needed to exploit the flaw when it is on.
  • The flaw allows an attacker to add their own trusted key with no expiry, which Quay then accepts for any repository.
  • With tokens signed by the planted key, an attacker can retrieve private images, secrets, and push or overwrite images.
  • A second critical flaw lets a user who can create a namespace steal other tenants' robot account tokens via SQL LIKE wildcard matching.
  • The namespace flaw builds an SQL LIKE pattern without escaping wildcards, so an underscore can match another tenant's namespace.
  • Red Hat lists every version of Quay 3 and Quay 5 as affected by both flaws, including standalone, Operator-deployed, and mirror registry deployments.

What is affected?

  • All versions of Quay 3 and Quay 5, including standalone installs, Quay Operator on OpenShift, and mirror registry for Red Hat OpenShift.

How do I fix or mitigate it?

  1. Block the /keys endpoint at the proxy or load balancer except for trusted internal components.
  2. Search audit logs for service_key_rotate and service_key_delete events where expiration_date is null and remove unrecognized approved service keys.

What should defenders look for?

  • Audit log entries for service_key_rotate or service_key_delete with expiration_date set to null.
  • Presence of unrecognized approved service keys in the registry.
  • Unexpected robot account token usage or pulls and pushes that do not match normal robot behavior.

Summarised by SecOraLens from The Hacker News. Always read the original source before acting. How SecOraLens verifies advisories.

What to do next

For CISOs and SOC leads

Brief your board. Brief your team.

Executive risk briefs for governance, technical kill-chains for the SOC — delivered as advisories publish. Critical alerts within 1 hour. No spam, unsubscribe anytime.