How severe is GHSA-5g4r-87v2-jqvx?

No CVSS score has been assigned to GHSA-5g4r-87v2-jqvx yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-5g4r-87v2-jqvx?

GHSA-5g4r-87v2-jqvx affects the following packages: apk-parser (npm). Ecosystems affected: npm.

How do I fix GHSA-5g4r-87v2-jqvx?

Update apk-parser to 0.1.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5g4r-87v2-jqvx is resolved across your whole dependency graph.

How do I detect GHSA-5g4r-87v2-jqvx in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for apk-parser. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-5g4r-87v2-jqvx if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-5g4r-87v2-jqvx?

O3 pinpoints whether GHSA-5g4r-87v2-jqvx is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-5g4r-87v2-jqvx actively exploited in the wild?

No public exploit code has been indexed for GHSA-5g4r-87v2-jqvx yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-5g4r-87v2-jqvx published, and has it been updated?

GHSA-5g4r-87v2-jqvx was published on September 1, 2020 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-5g4r-87v2-jqvx

GHSA-5g4r-87v2-jqvx is a remote code execution vulnerability in apk-parser. O3 Security confirms whether GHSA-5g4r-87v2-jqvx is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Downloads Resources over HTTP in apk-parser

Also known asCVE-2016-10564

Published

Sep 1, 2020

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

1other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

apk-parsernpm

142downloads / week

Description

apk-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.

Recommendation

Update to version 0.1.6 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`apk-parser`	all versions	0.1.6

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for apk-parser. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update apk-parser to 0.1.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5g4r-87v2-jqvx is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-5g4r-87v2-jqvx is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-5g4r-87v2-jqvx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

apk-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. ## Recommendation Update to version 0.1.6 or later.

O3 Security · Impact-Aware SCA

Is GHSA-5g4r-87v2-jqvx in your dependencies?

O3 detects GHSA-5g4r-87v2-jqvx across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works