CVE-2019-9601
Description
The ApowerManager application through 3.1.7 for Android allows remote attackers to cause a denial of service via many simultaneous /?Key=PhoneRequestAuthorization requests.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
ApowerManager for Android ≤3.1.7 is vulnerable to remote denial of service via many simultaneous requests to /?Key=PhoneRequestAuthorization.
Vulnerability
The ApowerManager application for Android (versions through 3.1.7) exposes an HTTP server on port 2333. Sending a large number of simultaneous POST requests to the endpoint /?Key=PhoneRequestAuthorization causes the application to crash, resulting in a denial of service [1]. No authentication or special privileges are required to reach this endpoint.
Exploitation
An attacker with network access to the device can send many concurrent POST requests to http://<target_ip>:2333/?Key=PhoneRequestAuthorization. The public exploit [1] demonstrates using 10,000 threads to flood the server, overwhelming the application and causing it to become unresponsive or terminate.
Impact
Successful exploitation leads to a denial of service: the ApowerManager application crashes or becomes unresponsive, preventing legitimate use of the phone management features. No data is compromised, but availability is severely impacted.
Mitigation
As of the publication date, no official patch has been released for this vulnerability. Users should consider blocking network access to port 2333 on the device or restricting the application's network permissions. Upgrading to a version newer than 3.1.7 may resolve the issue if the vendor has silently fixed it, but no advisory confirms this [1].
AI Insight generated on May 26, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1- Range: <=3.1.7
Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
2- www.exploit-db.com/exploits/46380mitreexploitx_refsource_EXPLOIT-DB
- www.youtube.com/watchmitrex_refsource_MISC
News mentions
0No linked articles in our index yet.