ZeroHour
Security Affairspublished ()ingested @securityaffairs

AbstractEmu, a new Android malware with rooting capabilities

Vulnerabilities mentionedAll →

CVEVulnerabilityCVSSEPSSFlagsAffectedExposurePublished
CVE-2019-2215
Use-After-Free Privilege Escalation in Android Kernel (CVE-2019-2215)

CVE-2019-2215 is a use-after-free flaw (CWE-416) in the Android kernel's binder.c IPC driver that allows privilege escalation from an application to the Linux kernel. Exploitation requires no user interaction, but an attacker must either run a malicious local application or chain the bug with a vulnerability in a network-facing application. Successful exploitation yields kernel-level code execution, effectively rooting the device and giving the attacker full control over apps, data, and communications. Affected parties include Android devices with unpatched kernels (reporting at the time indicated most Android phones were affected), plus products shipping affected Android kernel code, including Google Android, Debian/Ubuntu builds, and NetApp and Huawei offerings. The flaw was publicly disclosed and patched in Android's October 2019 security updates, public proof-of-concept exploits exist, and it is listed in CISA's Known Exploited Vulnerabilities catalog with a high (72.1%) EPSS probability of exploitation; headlines confirm in-the-wild use, including a Google Play app that leveraged it to deliver spyware.

Do: Apply vendor-supplied updates per CISA's required action — for phones and tablets, ensure the device is on the October 2019 Android security patch level or later (check Settings > About phone > Android security patch level) and patch via MDM across your fleet; NetApp, Huawei, Debian, and Ubuntu customers should install their vendors' corresponding kernel updates. Because this is a local privilege escalation with no user interaction required, also patch any network-facing applications that could be chained with it, and hunt for signs of exploitation such as unexpected root or unknown sideloaded/rooting apps on managed devices.

7.872% KEV PoC ×2
  • google android (Android kernel, binder.c)
  • huawei android (Android-based devices)
  • debian linux (Android kernel code)
  • +9 more
massbillions of devices
CVE-2020-0041
Out-of-Bounds Write in Android Kernel Binder Driver Enables Local Privilege Escalation

CVE-2020-0041 is an out-of-bounds write in the binder_transaction function of the Android kernel's binder.c, caused by an incorrect bounds check in the binder IPC driver. It is triggered locally: code already on the device, such as an unprivileged app or process, can issue a maliciously crafted binder transaction with no user interaction and no additional execution privileges required. A successful exploit escalates a local attacker from app-level privileges to kernel-level code execution, giving full read/write control of the device — the same type of primitive used by rooting malware seen in recent Android threats. Affected products are Android devices running kernel builds without the upstream binder fix; Google is the listed vendor, and because the flaw sits in the shared Android kernel it potentially spans many OEM device models rather than a single product. CISA added the CVE to the Known Exploited Vulnerabilities catalog on 2021-11-03, indicating known exploitation in the wild, though no public PoC is known and EPSS estimates roughly a 3% chance of exploitation in any 30-day window.

Do: Apply the kernel/binder patch by installing your device OEM's latest Android security update, consistent with CISA KEV's required action to apply updates per vendor instructions, and verify the device is on a current security patch level. There is no known mitigation short of patching the binder driver, so prioritize devices that install untrusted apps, where local attackers have an execution foothold. The rooting malware activity in recent headlines is not confirmed in this data to exploit CVE-2020-0041, but patching eliminates the kernel LPE primitive such malware relies on.

7.83% KEV
  • Google Android (kernel, binder driver) Android kernel builds without the upstream binder.c fix; CISA lists 'Android Android Kernel' with no specific kernel version ranges provided in the source data
mass≈ billions of Android devices potentially affected (Android's global active install base is on the order of 3 billion devices)
CVE-2020-0069
Out-of-Bounds Write in MediaTek Command Queue Driver Enables Android Privilege Escalation

CVE-2020-0069 is an out-of-bounds write (CWE-787) in the ioctl handlers of the MediaTek Command Queue kernel driver on Android, caused by insufficient input validation and missing SELinux restrictions. Any application running locally can trigger the flaw by sending maliciously crafted ioctl requests, and no special permissions or user interaction are required. A successful exploit corrupts kernel memory and achieves local escalation of privilege, giving the attacker root-level control of the device. Affected users are owners of Android phones built on the multiple MediaTek chipsets named by CISA, spanning Google Android and numerous Huawei/Honor firmware builds (including Honor 20 Pro, Nova 3, Y6 2019, and Berkeley/Columbia/Cornell/Dura firmware variants). The flaw is confirmed as exploited in the wild via CISA's KEV catalog (added 2021-11-03, with ransomware use listed as unknown), EPSS estimates a 1.4% probability of exploitation within 30 days, no public PoC is cataloged, and the KEV listing coincided with reports of rooting malware such as AbstractEmu capable of gaining root on Android devices.

Do: Apply the latest vendor firmware / Android security update per vendor instructions, as required by the CISA KEV entry, and verify the device shows a current Android security patch level in Settings > About phone. Because exploitation requires a locally installed app, avoid installing untrusted or sideloaded apps on unpatched MediaTek-based devices as an interim mitigation. Organizations should inventory MediaTek-powered handsets, including the listed Huawei/Honor models, and prioritize patching them given confirmed in-the-wild exploitation.

7.81% KEV
  • MediaTek Chipset list not enumerated in source data; affected Android kernel builds fixed via vendor security updates
  • Google Android Android kernel (affected Android release versions not enumerated in source data)
  • Huawei Berkeley-L09 firmware
  • +9 more
mass≈100M+ devices (order of magnitude: hundreds of millions of MediaTek-based Android handsets; exact count unknown)
Full article406 words · extracted from securityaffairs.com · click to collapse

AbstractEmu is a new Android malware that can root infected devices to take complete control and evade detection with different tricks.

Security researchers at the Lookout Threat Labs have discovered a new Android malware, dubbed AbstractEmu, with rooting capabilities that is distributed on Google Play and prominent third-party stores (i.e. Amazon Appstore and the Samsung Galaxy Store).

The malware code abstraction and anti-emulation checks of avoid analysis.

“We named the malware “AbstractEmu” after its use of code abstraction and anti-emulation checks to avoid running while under analysis. A total of 19 related applications were uncovered, seven of which contain rooting functionality, including one on Play that had more than 10,000 downloads.” reads the analysis published by the researchers.

The experts discovered 19 utility apps containing the malicious code that were distributed via Google Play and third-party app stores. Some of these apps had thousands of downlods.

Google quickly removed the tainted apps from its store after Lookout shared its findings.

Experts pointed out that rooting malware is rare as dangerous, they can allow attackers to gain root access to the device and perform malicious activities without user interaction.

The experts speculate AbstractEmu was developed by a well-resourced group with financial motivation. Their code-base and evasion techniques used by the threat actors are quite sophisticated. 

“AbstractEmu does not exploit zero-click remote exploits, instead it exploits very contemporary vulnerabilities (CVE-2020-0041, CVE-2020-0069, CVE-2019-2215 and CVE-2020-0041) from 2019 and 2020 to target the largest number of devices as possible.  

Once installed the AbstractEmu malware, it will begin harvesting and sending system information to C2 while the malware waiting for further commands.

Experts noticed that the extensive permissions granted through root access also give the attackers common permissions used by banking trojans to receive any two-factor authentication codes sent via SMS, or run in the background and launch phishing attacks. Some of the permissions obtained by the malware also allow for remote interactions with the device, such as capturing content on the screen and accessing accessibility services, which enables attackers to interact with other apps on the device. The researchers found similarities with the Anatsa and Vultur malware families.

“Rooting Android or jailbreaking iOS devices are still the most invasive ways to fully compromise a mobile device.”  concludes the report that also includes indicators of compromise (IoCs).

Follow me on Twitter: @securityaffairs and Facebook

[adrotate banner=”9″][adrotate banner=”12″]

Pierluigi Paganini

(SecurityAffairs – hacking, cybercrime)

[adrotate banner=”5″]

[adrotate banner=”13″]



Text extracted automatically; images, tables and formatting may be missing. Original: https://securityaffairs.com/123873/malware/abstractemu-android-malware.html