Google detects Android Tizi Spyware that spies on popular apps like WhatsApp and Telegram
Vulnerabilities mentionedAll →
| CVE | Vulnerability | CVSS | EPSS | Flags | Affected | Exposure | Published |
|---|---|---|---|---|---|---|---|
| CVE-2013-2094 | Out-of-Bounds Access in Linux Kernel perf Events Enables Privilege Escalation The Linux kernel's perf event subsystem fails to validate all 64 bits of the attr.config value supplied from user space, causing an out-of-bounds access to the perf_swevent_enabled array in sw_perf_event_destroy(). A local attacker triggers the flaw by creating a perf event with a crafted attr.config value, and the out-of-bounds access occurs when that event is destroyed, corrupting adjacent kernel memory. By corrupting memory this way, an attacker can escalate privileges from an unprivileged local user to kernel-level (root) privileges on the affected system. Any system running an affected Linux kernel where perf events are available is exposed; the provided data does not specify exact affected kernel version ranges, so operators should confirm against vendor advisories. The vulnerability is actively exploited: it was added to CISA's Known Exploited Vulnerabilities catalog on 2022-09-15, and EPSS assigns it a 47.7% probability of exploitation within 30 days (99th percentile). Do: Apply kernel updates per vendor instructions as required by CISA, then reboot so the system runs the patched kernel. As interim mitigation, restrict unprivileged access to perf events (e.g., by raising the perf_event_paranoid sysctl) and limit untrusted local shell access. Verify the running kernel version against your distribution's advisory for this CVE before and after remediation. | — | 48% | KEV |
| masspotentially millions of Linux systems (kernel ubiquity across servers, cloud instances, and embedded devices; exact count of systems running the vulnerable… | |
| CVE-2013-2596 | Integer Overflow in Linux Kernel fb_mmap Enables Privilege Escalation CVE-2013-2596 is an integer overflow in the fb_mmap function in drivers/video/fbmem.c of the Linux kernel, a memory-mapping routine for framebuffer devices. The flaw is triggered when the kernel performs the arithmetic used to map framebuffer memory, and the overflowed calculation can yield an incorrect mapping that an attacker can leverage. An attacker who successfully exploits it gains elevated privileges on the affected system. Any system running an affected Linux kernel build is exposed, with the practical attack surface concentrated on systems where users can memory-map framebuffer devices; the specific vulnerable version range is not specified in the available data. The flaw was added to CISA's Known Exploited Vulnerabilities catalog on 2022-09-15, indicating exploitation in the wild, though no public proof-of-concept is known, ransomware use is unknown, and EPSS puts 30-day exploitation probability at 3.2% (87th percentile). Do: Apply updated kernel packages per your distribution or vendor's instructions, as CISA's required action directs, prioritizing internet-exposed and multi-user systems. As an interim mitigation, audit which systems permit unprivileged access to framebuffer devices (/dev/fb*) and restrict that access. Because fixed version numbers are not specified in the available data, confirm exact patched kernel versions with your vendor before declaring remediation complete. | — | 3% | KEV |
| massPotentially billions of Linux-powered devices (servers, Android handsets, embedded systems) run affected kernel code, though practical exploitability is… | |
| CVE-2013-2597 | Stack Buffer Overflow in Code Aurora ACDB Audio Driver Enables Privilege Escalation A stack-based buffer overflow (CWE-119) exists in the audio calibration database (acdb) audio driver from Code Aurora, the code incorporated into third-party products such as Qualcomm and Android. An attacker who can get crafted input to this driver can overwrite stack memory and escalate privileges to a higher-than-intended level on the device. Any device shipping the vulnerable Code Aurora ACDB audio driver — notably Qualcomm-powered Android products — is potentially affected, though the available data does not specify affected version ranges. Exploitation is confirmed in the wild: CISA added the flaw to the Known Exploited Vulnerabilities catalog on 2022-09-15, while EPSS estimates a 1.5% probability of exploitation in the next 30 days and no public proof-of-concept is known. Do: Apply updated audio drivers/firmware from your chipset or device vendor as soon as available, per CISA's required action to apply updates per vendor instructions, and check Qualcomm and Android security bulletins for fixes covering CVE-2013-2597. Because this is a local privilege escalation, prioritize Qualcomm-based Android devices where untrusted apps or users can execute code, and limit installation of untrusted applications on affected devices until patched. | — | 2% | KEV |
| masshundreds of millions to billions of devices (Qualcomm-based Android hardware) | |
| CVE-2013-6282 | Improper Input Validation in Linux Kernel on ARM Enables Privilege Escalation CVE-2013-6282 is an improper input validation flaw (CWE-20) in the Linux kernel's get_user and put_user API functions, which on ARM v6k/v7 platforms fail to validate the target address before accessing it. When kernel code uses these functions with an application-supplied pointer, the address is not verified as user space, so a local application can supply a kernel-space address (for example via system calls or ioctls) and read and write kernel memory. An attacker who can already run code on the device can leverage this kernel memory access to escalate privileges to root/kernel level, which can enable persistence or further post-exploitation activity. Affected systems are Linux kernels running on ARM v6k/v7 processors, the architecture that dominated Android smartphones and much embedded Linux hardware in that era; the source data does not enumerate specific affected kernel version ranges. Despite the flaw's 2013 origin, CISA added it to the Known Exploited Vulnerabilities catalog on 2022-09-15, confirming exploitation in the wild, with EPSS estimating a 39.7% probability of exploitation within 30 days (99th percentile). Do: Apply updates per vendor instructions (CISA required action): upgrade the Linux kernel on ARM v6k/v7 devices to a vendor-patched version and install OEM/Google security updates on Android devices, checking vendor advisories for the fixed kernel builds. Inventory legacy and internet-exposed ARM-based embedded systems still running old kernels, and because this is a local privilege escalation, restrict execution of untrusted applications and code on affected devices. | — | 40% | KEV |
| masshundreds of millions of ARM v6k/v7-based devices (legacy Android smartphones and embedded Linux systems) | |
| CVE-2014-3153 | Local Privilege Escalation in Linux Kernel futex_requeue (CVE-2014-3153) CVE-2014-3153 is a local privilege escalation flaw in the futex_requeue function of kernel/futex.c in the Linux kernel, where the code does not ensure that a requeue operation involves two different futex addresses. A local, unprivileged user triggers it by issuing crafted futex system calls that requeue a futex back to the same address, corrupting kernel state in the futex priority-inheritance queue. An attacker who exploits it can execute code with kernel-level (root) privileges, fully compromising the host without any network access; the bug was also the basis of the 2014 'Towelroot' one-click Android rooting exploit. Any Linux system running an affected, unpatched kernel is exposed - servers, Android handsets, and embedded devices - although exploitation requires the ability to run code locally on the target. The vulnerability is listed in CISA KEV (added 2022-05-25), indicating known in-the-wild exploitation, with EPSS at 37.2% (98th percentile) and no public PoC catalogued in the source data. Do: Apply kernel updates per vendor instructions (CISA required action): upgrade affected Linux systems to a kernel release from your distribution that includes the futex fix, and confirm the running version with 'uname -r' against your vendor's advisory. Because exploitation requires local code execution, prioritize multi-tenant servers, shared/embedded appliances, and Android device fleets where untrusted users or apps run locally, and monitor those systems for signs of local privilege escalation until patched. | — | 37% | KEV |
| masshundreds of millions of devices (Linux servers plus Android handsets and embedded systems running unpatched 2014-era kernels) |
Full article594 words · extracted from securityaffairs.com · click to collapse
Pierluigi Paganini
November 28, 2017

Google identified a new family of Android malware dubbed Tizi spyware by using Google Play Protect, it spies on popular apps like WhatsApp and Telegram.
In May, Google introduced the defense system called Google Play Protect to protect the Android devices, it implements a machine learning and app usage analysis to identify any malicious activity on the mobile device.
Recently, Google identified a new family of Android malware dubbed Tizi spyware by using Google Play Protect. Tizi infected targeted devices in African countries, specifically in Kenya, Nigeria, and Tanzania.
Tizi is a fully-featured Android backdoor with rooting capabilities that installs spyware to steal sensitive data from popular social media applications, including Facebook, Twitter, WhatsApp, Viber, Skype, LinkedIn, and Telegram.
“The Google Play Protect security team discovered this family in September 2017 when device scans found an app with rooting capabilities that exploited old vulnerabilities,” reads a blog post published by Google. “The team used this app to find more applications in the Tizi family, the oldest of which is from October 2015.”
The mobile apps infected with Tizi spyware are being advertised on social media websites and 3rd-party app stores.
Once installed on the target device, the malicious app gains root access to install spyware, then the malicious code contacts the command-and-control servers by sending an SMS text message with the GPS coordinates of the infected device to a specific number.Experts discovered that the Tizi malware is installed by the backdoor that exploits known vulnerabilities, including CVE-2012-4220, CVE-2013-2596, CVE-2013-2597, CVE-2013-2595, CVE-2013-2094, CVE-2013-6282, CVE-2014-3153, CVE-2015-3636, and CVE-2015-1805.
If none of the above flaws could be used to install the Tizi spyware, the backdoor will attempt to perform some actions get higher privileges, for example asking the user to grant them.
“If a Tizi app is unable to take control of a device because the vulnerabilities it tries to use are are all patched, it will still attempt to perform some actions through the high level of permissions it asks the user to grant to it, mainly around reading and sending SMS messages and monitoring, redirecting, and preventing outgoing phone calls.” continues Google.
The Tizi spyware is able to communicate with the command-and-control servers over regular HTTPS, and also through the MQTT messaging protocol using a custom server.
The Tizi spyware contains various capabilities common to commercial spyware:
- Stealing data from popular social media platforms, including Facebook, Twitter, WhatsApp, Viber, Skype, LinkedIn, and Telegram.
- Recording calls from WhatsApp, Viber, and Skype.
- Sending and receive SMS messages.
- Accessing calendar events, call log, contacts, photos, and list of installed apps
- Stealing Wi-Fi encryption keys.
- Recording ambient audio and take pictures without displaying the image on the device’s screen.
Google has identified 1,300 Android devices infected by Tizi and removed it, it also shared suggestions to reduce the chance of users’ devices being infected.
- Check permissions: Be cautious with apps that request unreasonable permissions. For example, a flashlight app shouldn’t need access to send SMS messages.
- Enable a secure lock screen: Pick a PIN, pattern, or password that is easy for you to remember and hard for others to guess.
- Update your device: Keep your device up-to-date with the latest security patches. Tizi exploited older and publicly known security vulnerabilities, so devices that have up-to-date security patches are less exposed to this kind of attack.
- Google Play Protect: Ensure Google Play Protect is enabled.
- Locate your device: Practice finding your device, because you are far more likely to lose your device than install a PHA.
Text extracted automatically; images, tables and formatting may be missing. Original: https://securityaffairs.com/66116/malware/android-tizi-spyware.html