CVE-2024-31320 is a privilege-escalation vulnerability in the Android Framework component. The flaw is in the setSkipPrompt logic of AssociationRequest.java and allows a companion device association to be established without the expected user confirmation through the Companion Device Manager (CDM) workflow. By bypassing the confirmation step, a local attacker can abuse the association process and obtain elevated privileges. The issue does not require user interaction and does not require additional execution privileges beyond local access to the vulnerable device.
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 contains two Frida JavaScript scripts targeting CVE-2024-31320 on Android devices. The first script (Exploit_CVE.js) abuses the CompanionDeviceManager API to trigger Bluetooth device pairing with a specified MAC address without user interaction, potentially allowing unauthorized device association. The second script (steal_info.js) hooks into system services to steal sensitive information: it intercepts geolocation data via LocationManager and notification content via NotificationListenerService. Both scripts require Frida and are intended to be run on a rooted device or emulator with the appropriate target apps. The exploit demonstrates both privilege abuse (automated pairing) and data exfiltration (location, notifications), making it a practical operational exploit for local attackers with device access.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.