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

> Attackers can access sensitive database information because the default secret key is hardcoded in plain text during initial configuration.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Apr 2024
- **Updated:** 21 Jan 2026
- **Also known as:** GHSA-frqc-23qh-4rq8

## What is CVE-2024-3623?

CVE-2024-3623 is a medium-severity vulnerability in mirror registry for Red Hat OpenShift, published on 25 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.

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

Weakness: CWE-256 (Plaintext Storage of a Password)

## Which versions are affected by CVE-2024-3623?

It affects 1 product.


Products: Redhat Mirror Registry.

## How do I fix CVE-2024-3623?

No fix has been published for CVE-2024-3623 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-3623 being exploited?

There is no known exploitation of CVE-2024-3623 in the wild and no public exploit code.

## Other vulnerabilities in mirror registry for Red Hat OpenShift

- [CVE-2024-3622](https://insights.sbomify.com/CVE-2024-3622/): Mirror-registry: plain-text default csrf secret key (high 8.8)
- [CVE-2026-2376](https://insights.sbomify.com/CVE-2026-2376/): Mirror-registry: quay: quay: server-side request forgery via open redirect vulnerability in web interface (medium 4.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-3623 and fix it if it is affected.

What it is: CVE-2024-3623 is a medium-severity vulnerability in mirror registry for Red Hat OpenShift, published on 25 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-3623 in the wild and no public exploit code.

Affected product: mirror registry for Red Hat OpenShift. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-3623/ (Markdown: https://insights.sbomify.com/CVE-2024-3623/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-3623
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-3623
- OSV: https://osv.dev/vulnerability/CVE-2024-3623

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-3623/
Summaries are generated and may contain mistakes; the official description above is the record.