Skip to content
Fencer Intel
low —

GHSA-jf2q-463c-6f52 json

androidqf: Zip entry Name Injection in APK bundle (Zip Slip for zip consumers)

published 5mo ago modified 4mo ago also GO-2026-5464

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### Summary `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.

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

### Patched version [1.8.3](https://github.com/mvt-project/androidqf/releases/tag/v1.8.3)

### Credits This issue was identified during a security assessment conducted by 0xche.

Patch / fix

  • go github.com/mvt-project/androidqf 1.8.3

Is GHSA-jf2q-463c-6f52 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
go github.com/mvt-project/androidqf
<1.8.3
1.8.3

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.