# CVE-2024-3624: Mirror-registry: database user and password stored in plain-text

> Attackers with file access can read plain-text database credentials from the configuration file, gaining unauthorized access to the Quay database.

- **Severity:** High 7.3 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Apr 2024
- **Updated:** 20 Nov 2025
- **Also known as:** GHSA-4cpq-x93q-3px9

## What is CVE-2024-3624?

CVE-2024-3624 is a high-severity vulnerability in mirror registry for Red Hat OpenShift, published on 25 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

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

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


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

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

## Is CVE-2024-3624 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-3624 is a high-severity vulnerability in mirror registry for Red Hat OpenShift, published on 25 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-3624 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-3624/ (Markdown: https://insights.sbomify.com/CVE-2024-3624/index.md)
```

## Sources

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

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