Skip to content

← Actionable
Low, CVSS 1.1

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

GHSA-jf2q-463c-6f52

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/mvt-project/androidqf 1.8.3), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
1.1 · CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U · score source
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

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 Credits This issue was identified during a security assessment conducted by 0xche.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-jf2q-463c-6f52

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-jf2q-463c-6f52

Advisory: androidqf: Zip entry Name Injection in APK bundle (Zip Slip for zip consumers)
IDs: GHSA-jf2q-463c-6f52
Record: https://patchnext.com/advisories/ghsa-jf2q-463c-6f52 (revision 1, source checked 26 Oct 2026, 15:22 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 1.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/mvt-project/androidqf 1.8.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/mvt-project/androidqf: affected <= 1.8.2; fixed in 1.8.3

## Suggested inspection (read-only)
- Go github.com/mvt-project/androidqf: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/mvt-project/androidqf.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-jf2q-463c-6f52 (GitHub-reviewed advisory GHSA-jf2q-463c-6f52 lists affected ranges: Go github.com/mvt-project/androidqf >=0 <=1.8.2)

Commands are suggestions: review each one before running it.

Loading voting…