Improper Protection of WhatsApp Noise Authentication Key on iOS
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Meta Platforms, Inc. | WhatsApp Messenger for iOS | unknown |
|
No data.
No data.
No data available yet.
Vendor Solution
Remove the unwrapped file copy of the transport authentication private key from the shared application container, or hold it only under a protection class that requires the device passcode and hardware backing. Binding the transport authentication key to device attestation, so that a copy of the key alone does not authenticate a session from a different device, removes the impact described above.
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Cleartext storage of the WhatsApp Noise static private key in the shared application container (cck.dat) in WhatsApp Messenger for iOS allows an attacker with access to a full filesystem extraction or equivalent application data copy to recover long-term authentication material and impersonate the victim account. | |
| Title | Improper Protection of WhatsApp Noise Authentication Key on iOS | |
| Weaknesses | CWE-312 | |
| References |
| |
| Metrics |
cvssV4_0
|