CVE-2016-10564
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedapk-parser is a tool to extract Android Manifest info from an APK file. apk-parser versions below 0.1.6 download binary resources over HTTP, which leaves it vulnerable to MITM attacks. It may be possible to cause remote code execution (RCE) by swapping out the requested binary with an attacker controlled binary if the attacker is on the network or positioned in between the user and the remote server.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceapk-parser versions below 0.1.6 download binary resources over unencrypted HTTP, allowing man-in-the-middle attackers to intercept and modify these downloads. An attacker positioned on the network could substitute malicious binaries during download, potentially achieving remote code execution on systems using this library.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 0.1.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate apk-parser in your project dependenciesCheck your package.json file for apk-parser in the dependencies or devDependencies section, or run 'npm list apk-parser' to see the installed versionAffected if apk-parser is listed as a dependency
-
Identify the exact installed versionRun 'npm list apk-parser --depth=0' or check the node_modules/apk-parser/package.json file for the version fieldAffected if The version number displayed is below 0.1.6 (e.g., 0.1.5, 0.1.4, etc.)
-
Inspect the library source for HTTP URLsSearch the node_modules/apk-parser directory for any URLs using 'http://' instead of 'https://' (e.g., grep -r "http://" node_modules/apk-parser/)Affected if The library contains URLs starting with http:// for downloading binary resources
-
Monitor network traffic during library usageUse a network proxy or packet capture tool (such as Wireshark or Burp Suite) while executing code that uses apk-parser to parse an APK fileAffected if The library makes outbound HTTP requests to download resources rather than HTTPS
You are affected if apk-parser version is below 0.1.6 AND your application uses the library to parse APKs, allowing potential interception of binary downloads over unencrypted HTTP.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data0.1.6
Update apk-parser to version 0.1.6 or later, which uses HTTPS for resource downloads. If immediate update is not possible, implement TLS/SSL inspection or network-level controls to mitigate MITM risks until the library can be patched.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10564 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-10564 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data