Skip to content

react-native-mmkv Insertion of Sensitive Information into Log File vulnerability

Moderate severity GitHub Reviewed Published Jan 9, 2024 in mrousavy/react-native-mmkv • Updated Jan 19, 2024

Package

npm react-native-mmkv (npm)

Affected versions

< 2.11.0

Patched versions

2.11.0

Description

Summary

Before version v2.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.

Details

The bridge for communicating between JS code and native code on Android logs the encryption key. This was fixed in commit a8995cc by only logging whether encryption is used.

Impact

The encryption of an MMKV database protects data from higher privilege processes on the phone that can access the app storage. Additionally, if data in the app's storage is encrypted, it is also encrypted in potential backups.
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.

The bug was discovered and fixed by somebody else. Not me. I'm just reporting this so users of react-native-mmkv upgrade the dependency.

References

@mrousavy mrousavy published to mrousavy/react-native-mmkv Jan 9, 2024
Published by the National Vulnerability Database Jan 9, 2024
Published to the GitHub Advisory Database Jan 9, 2024
Reviewed Jan 9, 2024
Last updated Jan 19, 2024

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.058%
(26th percentile)

Weaknesses

CVE ID

CVE-2024-21668

GHSA ID

GHSA-4jh3-6jhv-2mgp

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.