Database credential disclosure via plaintext configuration storage
Published Apr 25, 2024 · Updated Nov 20, 2025
Plaintext credential storage in Mirror Registry for Red Hat OpenShift allows local users to obtain Quay database access from config.yaml. The Jinja-generated configuration serializes DB_URI with an embedded database username and password as readable YAML rather than protecting them. An attacker must first gain access to the generated file; the exposed credentials then permit reading and altering Quay database data.
Summary
What happened
Plaintext credential storage in Mirror Registry for Red Hat OpenShift allows local users to obtain Quay database access from config.yaml. The Jinja-generated configuration serializes DB_URI with an embedded database username and password as readable YAML rather than protecting them. An attacker must first gain access to the generated file; the exposed credentials then permit reading and altering Quay database data.
The record
- CVE
- CVE-2024-3624
- Published
- Apr 25, 2024
- Updated
- Nov 20, 2025
- Vendor
- 389 Directory Server
- Product
- Mirror Registry for Red Hat OpenShift
- Classifications
- CWE-256, T1552.001
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 25, 2024CVE publishedPublication date reported by the CVE source.
- Nov 20, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo