CVE-2016-6564: Ragentek Android software contains an over-the-air update mechanism that communicates over an unencrypted channel, which can allow a remote attacker to execute…
Noroxi assessment
Priority: Monitor (action score 33/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 2.6% (FIRST EPSS); higher than 85.7% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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
- Published
- Jul 13, 2018
- Updated
- Jun 16, 2026
- EPSS
- 2.6% · 85th percentile
- CWE
- CWE-494
Report tools
Action score
33
Low priority for now.
- CVSS
- 32 / 40 · 8.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.6%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| infinixauthority | hot x507 firmware | cpe:2.3:o:infinixauthority:hot_x507_firmware |
| infinixauthority | hot x507 | cpe:2.3:h:infinixauthority:hot_x507 |
| infinixauthority | hot 2 x510 firmware | cpe:2.3:o:infinixauthority:hot_2_x510_firmware |
| infinixauthority | hot 2 x510 | cpe:2.3:h:infinixauthority:hot_2_x510 |
| infinixauthority | zero x506 firmware | cpe:2.3:o:infinixauthority:zero_x506_firmware |
| infinixauthority | zero x506 | cpe:2.3:h:infinixauthority:zero_x506 |
| infinixauthority | zero 2 x509 firmware | cpe:2.3:o:infinixauthority:zero_2_x509_firmware |
| infinixauthority | zero 2 x509 | cpe:2.3:h:infinixauthority:zero_2_x509 |
| bluproducts | studio g firmware | cpe:2.3:o:bluproducts:studio_g_firmware |
| bluproducts | studio g | cpe:2.3:h:bluproducts:studio_g |
| bluproducts | studio g plus firmware | cpe:2.3:o:bluproducts:studio_g_plus_firmware |
| bluproducts | studio g plus | cpe:2.3:h:bluproducts:studio_g_plus |
and 26 more
Versions reported by the vendor
Affected version ranges reported by the assigning authority (certcc). Independent of NVD's CPE analysis and usually ahead of it.
Ragentek Android software
- N/Aunknown
Affected versions · NVD (19)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- beeline pro 2 firmwareall versions
- bluproducts studio 6.0 hd firmwareall versions
- bluproducts studio c hd firmwareall versions
- bluproducts studio g firmwareall versions
- bluproducts studio g plus firmwareall versions
- bluproducts studio x firmwareall versions
- bluproducts studio x plus firmwareall versions
- doogee voyager 2 dg310i firmwareall versions
- iku-mobile colorful k45i firmwareall versions
- infinixauthority hot 2 x510 firmwareall versions
- infinixauthority hot x507 firmwareall versions
- infinixauthority zero 2 x509 firmwareall versions
- infinixauthority zero x506 firmwareall versions
- leagoo alfa 6 firmwareall versions
- leagoo lead 2s firmwareall versions
- leagoo lead 3i firmwareall versions
- leagoo lead 5 firmwareall versions
- leagoo lead 6 firmwareall versions
- xolo cube 5.0 firmwareall versions
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Dan Dahlberg and Tiago PereiraBitSight Technologies and Anubis Networks for reporting this vulnerability.
Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-494 · Download of Code Without Integrity CheckCVSS vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Software Integrity AttackCAPEC-184Low
- Malicious Software DownloadCAPEC-185Very High
- Malicious Software UpdateCAPEC-186High
- Malicious Automated Software Update via RedirectionCAPEC-187likelihood: High · High
- Malicious Manual Software UpdateCAPEC-533likelihood: Low · High
- Open-Source Library ManipulationCAPEC-538likelihood: Low · High
- Malicious Automated Software Update via SpoofingCAPEC-657likelihood: High · High
- Adversary in the Browser (AiTB)CAPEC-662likelihood: High · Very High
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.