CVE-2017-13209 is a local privilege escalation vulnerability in Android 8.0 and 8.1, specifically in the ServiceManager::add function of the hardware service manager. The vulnerability arises from an insecure permissions check that relies solely on the PID of the caller. This flaw allows a local application or service to register or replace a Hardware Abstraction Layer (HAL) service with its own, potentially malicious, implementation. As a result, an attacker can execute code as a privileged process 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 (1 hidden).
This repository contains a native Android C++ exploit/PoC binary, not a framework module. The project builds a binary named 'hwservice' from main.cpp and DummyService.cpp, with several generated-looking HIDL wrapper headers (BnHwDummyService.h, BpHwDummyService.h, BsDummyService.h, IDummyService.h, IHwDummyService.h) that support a fabricated HIDL service implementation. Repository structure: main.cpp is the primary entry point and orchestrates the exploit flow. It performs low-level Binder/HwBinder transactions against Android's hwservicemanager and token manager, including helper routines to find a hardware service, add/register a service, create or resolve tokens, and split execution into parent/child flows. DummyService.cpp implements the malicious/fake HIDL service object (IDummyService) and contains the core exploitation logic inside interfaceChain(), where it manipulates process lifecycle and triggers audio-service transactions to influence PID/service-manager state. The remaining headers are support code for the HIDL interface plumbing. The Makefile and Android.bp define Android/NDK builds, and the Makefile includes adb push/run helpers for deploying to /data/local/tmp/. Main exploit capability: the code attempts to register or replace a hardware service by abusing Android HIDL token management and hwservicemanager registration behavior. It directly invokes Binder transaction codes on IServiceManager (notably get/add style operations) and interacts with ITokenManager to obtain a binder from a token. The exploit then registers that binder under the 'default' service name. The fake service advertises itself as android.hidl.base@1.0::IBase rather than a legitimate custom interface, and even returns a fake hash chain, indicating deliberate service fabrication. Notable exploitation behavior: DummyService.cpp's interfaceChain() is weaponized as a trigger point. When called, it ensures sound effects are loaded via the 'audio' Binder service, kills a child process, waits for it, repeatedly forks to cycle process IDs toward a target PID, unloads and reloads sound effects, and sleeps to allow threads to spawn. Comments explicitly state the goal is to let system_server occupy a chosen PID so ACL checks pass, enabling service replacement. This strongly suggests a local privilege-escalation or service-impersonation exploit against Android's hardware service registration controls. There are no external network C2 endpoints, URLs, or IPs. The observable targets are Android Binder/HIDL interface names, service names, and local deployment paths. Overall, this is an operational local Android exploit PoC focused on Binder/HIDL service hijacking rather than remote exploitation.
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.