{"answers":{"affected":"2 open source packages ship an affected version, including react-native-mmkv. It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-21668 in the wild and no public exploit code.","fix":"Upgrade react-native-mmkv to 2.11.0 or later.","what":"CVE-2024-21668 is a medium-severity vulnerability in mrousavy react-native-mmkv, published on 9 Jan 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-21668 and fix it if it is affected.\n\nWhat it is: CVE-2024-21668 is a medium-severity vulnerability in mrousavy react-native-mmkv, published on 9 Jan 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-21668 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- react-native-mmkv (npm): affected all versions; fixed in 2.11.0\n- react-native-mmkv (npm): affected all versions; fixed in 2.11.0\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-21668/ (Markdown: https://insights.sbomify.com/CVE-2024-21668/index.md)","id":"CVE-2024-21668","markdown":"https://insights.sbomify.com/CVE-2024-21668/index.md","name":"CVE-2024-21668","record":{"aliases":["GHSA-4jh3-6jhv-2mgp"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"React Native MMKV library","requires_auth":"high_privilege","summary":"Attackers with ADB access can recover MMKV encryption keys from Android system logs, compromising data confidentiality in React Native apps.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"react-native-mmkv","vendor":"mrousavy"}],"cvss":{"score":4.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"react-native-mmkv is a library that allows easy use of MMKV inside React Native applications. Before version 2.11.0, the react-native-mmkv logged the optional encryption key for the MMKV database into the Android system log. The key can be obtained by anyone with access to the Android Debugging Bridge (ADB) if it is enabled in the phone settings. This bug is not present on iOS devices. By logging the encryption secret to the system logs, attackers can trivially recover the secret by enabling ADB and undermining an app's thread model. This issue has been patched in version 2.11.0.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Insertion of Sensitive Information into Log File in react-native-mmkv","id":"CVE-2024-21668","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":2,"n_references":3,"next":{"headline":"Hyperledger Aries Cloud Agent Python result of presentation verification not checked for LDP-VC","id":"CVE-2024-21669"},"packages":[{"ecosystem":"npm","fixed":["2.11.0"],"introduced":["0"],"last_affected":[],"package":"react-native-mmkv","purl":null,"source":"GHSA-4jh3-6jhv-2mgp"},{"ecosystem":"npm","fixed":["2.11.0"],"introduced":["0"],"last_affected":[],"package":"react-native-mmkv","purl":"pkg:npm/react-native-mmkv","source":"GHSA-4jh3-6jhv-2mgp"}],"prev":{"headline":"Pimcore Customer Data Framework Improper Access Control allows unprivileged user to access GDPR extracts","id":"CVE-2024-21667"},"products":["react-native-mmkv"],"published":"2024-01-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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-06-17","vendors":["mrousavy"]},"summary":"Attackers with ADB access can recover MMKV encryption keys from Android system logs, compromising data confidentiality in React Native apps.","url":"https://insights.sbomify.com/CVE-2024-21668/"}