First published: Wed Apr 10 2024(Updated: )
A flaw was found when using mirror-registry to install Quay. It uses a default database secret key, 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 database secret key. This flaw allows a malicious actor to access sensitive information from Quay's database.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Red Hat Quay for IBM Z and LinuxONE | ||
Red Hat mirror-registry |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-3623 is considered a high-severity vulnerability due to the exposure of a default database secret key in plain text.
To fix CVE-2024-3623, you should update your Quay and mirror-registry configurations to use a secure, unique database secret key instead of the default.
CVE-2024-3623 affects instances of Red Hat Quay and Red Hat mirror-registry that utilize the default database secret key.
The primary impact of CVE-2024-3623 is that it can lead to data exposure and unauthorized access to databases across multiple Quay instances.
While the best solution is to update the database secret key, a temporary workaround is to restrict access to the affected configuration files.