mirror registry for Red Hat OpenShift vulnerabilities
5 known vulnerabilities in mirror registry for Red Hat OpenShift from Red Hat. 5 are rated high or critical. Each entry lists the affected versions and the release that fixes it, where the vendor has published one.
Latest first
- 8.8 High severity
mirror registry for Red Hat OpenShift 2.0: Deserialization of Untrusted Data
A flaw was found in Red Hat Quay's handling of resumable container image layer uploads. The upload process stores intermediate data in the database using a format that, if tampered with, could allow an attacker to execute arbitrary code on the Quay server.
- 8.2 High severity
MIRROR-REGISTRY-2.0-RHEL-8: Incorrect Default Permissions
A flaw was found in the Mirror Registry. The quay-app container shipped as part of the Mirror Registry for OpenShift has write access to the `/etc/passwd`. This flaw allows a malicious actor with access to the container to modify the passwd file and elevate th
- 7.3 High severity
mirror registry for Red Hat OpenShift: Plaintext Storage of a Password
A flaw was found in Quay, where Quay's database is stored in plain text in mirror-registry on Jinja's config.yaml file. This issue leaves the possibility of a malicious actor with access to this file to gain access to Quay's Redis instance.
- 7.3 High severity
mirror registry for Red Hat OpenShift: Plaintext Storage of a Password
A flaw was found in how Quay's database is stored in plain-text in mirror-registry on the jinja's config.yaml file. This flaw allows a malicious actor with access to this file to gain access to Quay's database.
- 8.8 High severity
mirror registry for Red Hat OpenShift: Plaintext Storage of a Password
A flaw was found when using mirror-registry to install Quay. It uses a default secret, which is stored in plain-text format in one of the configuration template files. This issue may lead to all instances of Quay deployed using mirror-registry to have the same