# CVE-2016-6564: Code injection in Android software

> A hidden root binary in Ragentek Android devices communicates over HTTP, allowing remote attackers to execute arbitrary commands with root privileges.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jul 2018
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-cp5q-fwmj-pjgc

## What is CVE-2016-6564?

CVE-2016-6564 is a high-severity code injection vulnerability in Ragentek Android software, published on 13 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Android devices with code from Ragentek contain a privileged binary that performs over-the-air (OTA) update checks. Additionally, there are multiple techniques used to hide the execution of this binary. This behavior could be described as a rootkit. This binary, which resides as /system/bin/debugs, runs with root privileges and does not communicate over an encrypted channel. The binary has been shown to communicate with three hosts via HTTP: oyag[.]lhzbdvm[.]com oyag[.]prugskh[.]net oyag[.]prugskh[.]com Server responses to requests sent by the debugs binary include functionalities to execute arbitrary commands as root, install applications, or update configurations. Examples of a request sent by the client binary: POST /pagt/agent?data={"name":"c_regist","details":{...}} HTTP/1. 1 Host: 114.80.68.223 Connection: Close An example response from the server could be: HTTP/1.1 200 OK {"code": "01", "name": "push_commands", "details": {"server_id": "1" , "title": "Test Command", "comments": "Test", "commands": "touch /tmp/test"}} This binary is reported to be present in the following devices: BLU Studio G BLU Studio G Plus BLU Studio 6.0 HD BLU Studio X BLU Studio X Plus BLU Studio C HD Infinix Hot X507 Infinix Hot 2 X510 Infinix Zero X506 Infinix Zero 2 X509 DOOGEE Voyager 2 DG310 LEAGOO Lead 5 LEAGOO Lead 6 LEAGOO Lead 3i LEAGOO Lead 2S LEAGOO Alfa 6 IKU Colorful K45i Beeline Pro 2 XOLO Cube 5.0

Weakness: CWE-264, CWE-494 (Download of Code Without Integrity Check)

## Which versions are affected by CVE-2016-6564?

It affects 19 products.


Products: Beeline Pro 2 Firmware, Bluproducts Studio 6.0 Hd Firmware, Bluproducts Studio C Hd Firmware, Bluproducts Studio G Firmware, Bluproducts Studio G Plus Firmware, Bluproducts Studio X Firmware, Bluproducts Studio X Plus Firmware, Doogee Voyager 2 Dg310i Firmware, Iku-Mobile Colorful K45i Firmware, Infinixauthority Hot 2 X510 Firmware, Infinixauthority Hot X507 Firmware, Infinixauthority Zero 2 X509 Firmware, Infinixauthority Zero X506 Firmware, Leagoo Alfa 6 Firmware, Leagoo Lead 2s Firmware, Leagoo Lead 3i Firmware, Leagoo Lead 5 Firmware, Leagoo Lead 6 Firmware, Xolo Cube 5.0 Firmware.

## How do I fix CVE-2016-6564?

No fix has been published for CVE-2016-6564 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-6564 being exploited?

There is no known exploitation of CVE-2016-6564 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-6564 and fix it if it is affected.

What it is: CVE-2016-6564 is a high-severity code injection vulnerability in Ragentek Android software, published on 13 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-6564 in the wild and no public exploit code.

Affected product: Ragentek Android software. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-6564/ (Markdown: https://insights.sbomify.com/CVE-2016-6564/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-6564
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-6564
- OSV: https://osv.dev/vulnerability/CVE-2016-6564

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-6564/
Summaries are generated and may contain mistakes; the official description above is the record.