{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-3625 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-3625 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-3625 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."},"fix_prompt":"Check this codebase for CVE-2024-3625 and fix it if it is affected.\n\nWhat it is: CVE-2024-3625 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.\nExploitation: There is no known exploitation of CVE-2024-3625 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-3625/ (Markdown: https://insights.sbomify.com/CVE-2024-3625/index.md)","id":"CVE-2024-3625","markdown":"https://insights.sbomify.com/CVE-2024-3625/index.md","name":"CVE-2024-3625","record":{"aliases":["GHSA-87rm-wvwv-5r67"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"OpenShift mirror registry","requires_auth":"low_privilege","summary":"Attackers with file access can read plain-text Redis credentials from the configuration file to access the Quay database.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-256","name":"Plaintext Storage of a Password"}],"description":"A flaw was found in Quay, where Quay's database is stored in plain text in mirror-registry on Jinja's config.yaml file. This issue leaves the possibility of a malicious actor with access to this file to gain access to Quay's Redis instance.","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: redis password stored in plain-text","id":"CVE-2024-3625","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":"Missing authorization in Email Subscribers \u0026 Newsletters – Email Marketing, Post Notifications \u0026 Newsletter Plugin for WordPress","id":"CVE-2024-3626"},"packages":[],"prev":{"headline":"Mirror-registry: database user and password stored in plain-text","id":"CVE-2024-3624"},"products":["mirror registry for Red Hat OpenShift"],"published":"2024-04-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"2025-11-20","vendors":["Red Hat"]},"summary":"Attackers with file access can read plain-text Redis credentials from the configuration file to access the Quay database.","url":"https://insights.sbomify.com/CVE-2024-3625/"}