Summary
androidqf: APK download Path Traversal in device APK paths
During device acquisition, getPathToLocalCopy() constructs local filesystem paths for downloaded APKs using a filename component extracted by extractFileName(). The extraction splits on ==/ and takes the remainder without sanitization. If a compromised device returns a crafted APK path containing traversal sequences, filepath.Join resolves them, allowing the file to be written outside the intended apks/ directory.
Practical exploitability is limited because Android enforces strict package path formats under /data/app/ and does not allow apps to register paths containing traversal sequences. Rated Informational as a defense-in-depth concern.
Patched version
Credits
- This issue was identified during a security assessment conducted by 0xche.
- An additional vulnerability was independently identified by @0x0v1
Impact
An attacker with control of the connected device could potentially write files outside the expected output directory on the acquisition workstation, leading to arbitrary file overwrite with attacker-controlled content.
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-763J-3P5V-JFC6? GHSA-763J-3P5V-JFC6 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-763J-3P5V-JFC6? github.com/mvt-project/androidqf (go) versions <= 1.8.2 is affected.
- Is there a fix for GHSA-763J-3P5V-JFC6? Yes. GHSA-763J-3P5V-JFC6 is fixed in 1.8.3. Upgrade to this version or later.
- Is GHSA-763J-3P5V-JFC6 exploitable, and should I be worried? Whether GHSA-763J-3P5V-JFC6 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-763J-3P5V-JFC6 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-763J-3P5V-JFC6? Upgrade
github.com/mvt-project/androidqfto 1.8.3 or later.