Summary
androidqf: Zip entry Name Injection in APK bundle (Zip Slip for zip consumers)
generateZipPath() constructs zip entry names for collected APKs using device controlled content from extractFileName(). Since extractFileName() does not reject traversal sequences, the resulting zip entry name can contain ../. AndroidQF itself does not extract the zip it creates, but any forensic tool that extracts the acquisition bundle without zip-slip protection could write files to attacker chosen paths.
Patched version
Credits
This issue was identified during a security assessment conducted by 0xche.
Impact
A compromised device could inject path traversal sequences into the acquisition bundle's zip entry names. When a forensic analyst or forensic tooling extracts the bundle without entry name validation, files could be written outside the intended extraction directory.
Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-JF2Q-463C-6F52? GHSA-JF2Q-463C-6F52 is a low-severity path traversal vulnerability in github.com/mvt-project/androidqf (go), affecting versions <= 1.8.2. It is fixed in 1.8.3. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
- Which versions of github.com/mvt-project/androidqf are affected by GHSA-JF2Q-463C-6F52? github.com/mvt-project/androidqf (go) versions <= 1.8.2 is affected.
- Is there a fix for GHSA-JF2Q-463C-6F52? Yes. GHSA-JF2Q-463C-6F52 is fixed in 1.8.3. Upgrade to this version or later.
- Is GHSA-JF2Q-463C-6F52 exploitable, and should I be worried? Whether GHSA-JF2Q-463C-6F52 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-JF2Q-463C-6F52 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-JF2Q-463C-6F52? Upgrade
github.com/mvt-project/androidqfto 1.8.3 or later.