NVIDIA GeForce Now for Android contains a vulnerability in its game launcher component, where implicit intents intended for the streamer component can be intercepted and processed by a malicious application on the same device. This allows an attacker to exploit the intent handling mechanism to perform unauthorized actions.
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 two-app Android lab that reproduces the vulnerability pattern behind CVE-2023-31014 as an educational proof of concept, not a real GeForce NOW exploit. The structure contains a victim app and an attacker app. The victim app models a game launcher (victim/MainActivity) and a normal streamer component (victim/StreamerActivity). It builds an implicit intent with action lab.cve202331014.action.START_STREAM and attaches demo session data in extras: game ID, account alias, session ID, stream config, and stream endpoint. In the vulnerable path, startActivity(intent) is called without package or component targeting, allowing Android's resolver to offer any matching handler. The attacker app exposes HijackActivity via an exported intent-filter for the same action and default category. If selected, HijackActivity receives the victim extras, displays the captured values, and prevents the legitimate streamer from launching, demonstrating both information disclosure and denial of service. The fixed path in victim/MainActivity uses intent.setClass(this, StreamerActivity.class) before startActivity(), converting the flow to an explicit intent and blocking external interception. There is no real network exploitation, no remote C2, and no actual code execution chain; the payload is limited to local Android intent interception and display of intercepted data. The repository includes standard Gradle/Android project files, manifests for both apps, and Java source implementing the vulnerable flow, malicious handler, and mitigation example.
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.