Security readout for executives and security teams
Plain-English summary
apk-parser versions before 0.1.6 retrieved binary resources over unencrypted HTTP. A network-positioned attacker could replace that download with a malicious binary, potentially leading to remote code execution on the system using the package.
Executive priority
Treat this as a targeted supply-chain exposure in environments that use apk-parser. It is not listed as actively exploited, but the potential impact is serious if vulnerable tooling runs in CI or trusted developer systems.
Technical view
CVE-2016-10564 affects the HackerOne apk-parser Node module before 0.1.6. The weakness is cleartext transport of binary resources, mapped to CWE-311. The stated impact is possible RCE if an attacker can perform a man-in-the-middle substitution during the HTTP download.
Likely exposure
Exposure is most likely in development, CI, or automation environments using apk-parser versions below 0.1.6 to inspect Android APK manifests. Risk depends on whether the package performs the HTTP binary download in the environment and whether network traffic can be intercepted.
Exploitation context
The provided sources do not report active exploitation, and KEV status is false. Exploitation requires a network attacker or intermediary able to alter the binary downloaded over HTTP. The sources do not provide public exploit details or observed campaigns.
Researcher notes
Evidence is limited to the CVE record and Node Security advisory reference. The key validation point is the package version and whether HTTP binary retrieval occurs in your environment. Do not assume broader Android tooling exposure beyond the apk-parser Node module.
Mitigation direction
- Inventory Node dependencies for apk-parser versions below 0.1.6.
- Upgrade apk-parser to 0.1.6 or later where available.
- Avoid running vulnerable versions on untrusted or shared networks.
- Restrict build and analysis hosts from downloading binaries over HTTP.
- Check the vendor advisory for any additional guidance.
Validation and detection
- Review package manifests and lockfiles for apk-parser version entries.
- Confirm CI and developer environments do not use apk-parser below 0.1.6.
- Check build logs for apk-parser binary downloads over HTTP.
- Verify dependency scans flag CVE-2016-10564 where applicable.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-311: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2016-10564 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://nodesecurity.io/advisories/195CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Encryption of Sensitive Data
Missing Encryption of Sensitive Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.