Loading vulnerability…
CVE-2019-9465 is an information disclosure vulnerability in the handling of cryptographic operations by the Titan M security module on Android 10 devices. The vulnerability arises from an unusual root cause in the cryptographic processing, allowing a local attacker to access sensitive information without requiring additional execution privileges or user interaction.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a proof-of-concept Android application demonstrating CVE-2019-9465, a vulnerability in the Android StrongBox Keymaster implementation. The main code is in 'app/src/main/java/me/alexbakker/cve_2019_9465/MainActivity.java', which provides a user interface to configure key generation options (such as requiring user authentication, using random nonces, and enabling StrongBox). The app generates AES-GCM keys in the Android Keystore, optionally requiring biometric authentication, and performs encryption/decryption cycles to demonstrate the vulnerability. The exploit is local and requires the app to be run on a compatible Android device. No network endpoints are involved; the only fingerprintable endpoints are the use of the AndroidKeyStore and the key alias 'test'. The repository structure is typical for an Android Studio project, with build scripts, resource files, and a single main Java activity implementing the exploit logic.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.