CVE intelligence and bounded remediation
CVE-2016-6564 — Android devices with code from Ragentek contain a privileged binary that performs over-the-air (OTA) update checks
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…
- Severity
- High
- CVSS
- 9.3 (2.0)
- Published
- 2018-07-13
- CISA KEV
- Not currently listed
- Ecosystem
- operating-system
- Weaknesses
- CWE-494, CWE-264
Affected products
- infinixauthority / hot_x507_firmware
- infinixauthority / hot_2_x510_firmware
- infinixauthority / zero_x506_firmware
- infinixauthority / zero_2_x509_firmware
- bluproducts / studio_g_firmware
- bluproducts / studio_g_plus_firmware
Matched remediation archetype
Supply-chain, dependency, build, and update integrity
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Trace affected packages, source archives, build actions, plugins, installers, and updates from declared source to deployed artifact.
- Confirm provenance, signatures or digests, namespace ownership, lockfile resolution, registry configuration, and build-runner trust boundaries.
- Inventory direct, transitive, vendored, generated, and bundled copies across releases and distribution channels.
Remediate safely
- Move to a maintained trusted artifact or remove the dependency; pin immutable identities and verify provenance and integrity before use.
- Regenerate lockfiles and artifacts in a clean isolated build, minimize build credentials and network access, and produce an updated software bill of materials.
- Require reviewed update policy, protected publishing, and reproducible or independently attestable builds where supported.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.