{"answers":{"affected":"2 open source packages ship an affected version, including react-native-keys. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-45001 exists.","fix":"No fix has been published for CVE-2025-45001 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-45001 is a high-severity vulnerability in n/a, published on 9 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-45001 and fix it if it is affected.\n\nWhat it is: CVE-2025-45001 is a high-severity vulnerability in n/a, published on 9 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-45001 exists.\n\nAffected packages and fixed versions:\n- react-native-keys (npm): affected all versions up to 0.7.11; no fix listed\n- react-native-keys (npm): affected all versions up to 0.7.11; no fix listed\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-2025-45001/ (Markdown: https://insights.sbomify.com/CVE-2025-45001/index.md)","id":"CVE-2025-45001","markdown":"https://insights.sbomify.com/CVE-2025-45001/index.md","name":"CVE-2025-45001","record":{"aliases":["GHSA-fj44-h6xw-896g"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"React Native library","requires_auth":"none","summary":"Attackers can extract sensitive encryption keys and secrets from the compiled binary via static analysis, exposing protected data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"react-native-keys","vendor":"numan"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"}],"description":"react-native-keys 0.7.11 is vulnerable to sensitive information disclosure (remote) as encryption cipher and Base64 chunks are stored as plaintext in the compiled native binary. Attackers can extract these secrets using basic static analysis tools.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"react-native-keys insecurely stores encryption cipher and Base64 chunks","id":"CVE-2025-45001","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":2,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2025-45002"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.7.11"],"package":"react-native-keys","purl":null,"source":"GHSA-fj44-h6xw-896g"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.7.11"],"package":"react-native-keys","purl":"pkg:npm/react-native-keys","source":"GHSA-fj44-h6xw-896g"}],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2025-44998"},"products":["n/a"],"published":"2025-06-09","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-06-09","vendors":["n/a"]},"summary":"Attackers can extract sensitive encryption keys and secrets from the compiled binary via static analysis, exposing protected data.","url":"https://insights.sbomify.com/CVE-2025-45001/"}