{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-3623 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-3623 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2024-3623 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2024-3623 in the wild and no public exploit code.\n\nAffected product: mirror registry for Red Hat OpenShift. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-3623/ (Markdown: https://insights.sbomify.com/CVE-2024-3623/index.md)","id":"CVE-2024-3623","markdown":"https://insights.sbomify.com/CVE-2024-3623/index.md","name":"CVE-2024-3623","record":{"aliases":["GHSA-frqc-23qh-4rq8"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenShift mirror registry","requires_auth":"low_privilege","summary":"Attackers can access sensitive database information because the default secret key is hardcoded in plain text during initial configuration.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"mirror_registry","vendor":"redhat"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-256","name":"Plaintext Storage of a Password"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Mirror-registry: default database secret key stored in plain-text on initial configuration file","id":"CVE-2024-3623","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Mirror-registry: database user and password stored in plain-text","id":"CVE-2024-3624"},"packages":[],"prev":{"headline":"Mirror-registry: plain-text default csrf secret key","id":"CVE-2024-3622"},"products":["mirror registry for Red Hat OpenShift"],"published":"2024-04-25","related":[{"cvss_score":8.8,"headline":"Mirror-registry: plain-text default csrf secret key","id":"CVE-2024-3622","kev_date_added":null,"published":"2024-04-25"},{"cvss_score":4.9,"headline":"Mirror-registry: quay: quay: server-side request forgery via open redirect vulnerability in web interface","id":"CVE-2026-2376","kev_date_added":null,"published":"2026-03-12"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-01-21","vendors":["Red Hat"]},"summary":"Attackers can access sensitive database information because the default secret key is hardcoded in plain text during initial configuration.","url":"https://insights.sbomify.com/CVE-2024-3623/"}