Encryption-key disclosure via Android bridge logging
Published Jan 9, 2024 · Updated Jun 17, 2025
Sensitive-data exposure in react-native-mmkv before 2.11.0 allows local users to recover MMKV encryption keys from Android logs. The Android MmkvHostObject constructor passes the supplied cryptKey string to __android_log_print instead of recording only whether encryption is enabled. Exploitation requires high-privilege ADB access on an Android device with debugging enabled; the recovered key exposes encrypted app data and backups.
Summary
What happened
Sensitive-data exposure in react-native-mmkv before 2.11.0 allows local users to recover MMKV encryption keys from Android logs. The Android MmkvHostObject constructor passes the supplied cryptKey string to __android_log_print instead of recording only whether encryption is enabled. Exploitation requires high-privilege ADB access on an Android device with debugging enabled; the recovered key exposes encrypted app data and backups.
The record
- CVE
- CVE-2024-21668
- Published
- Jan 9, 2024
- Updated
- Jun 17, 2025
- Vendor
- Marc Rousavy
- Product
- react-native-mmkv
- Classifications
- CWE-532, CAPEC-215, T1533
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jan 9, 2024CVE publishedPublication date reported by the CVE source.
- Jun 17, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.11.0
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