GHSA-JF2Q-463C-6F52

Vulnerability from github – Published: 2026-05-21 17:09 – Updated: 2026-05-21 17:09
VLAI
Summary
androidqf: Zip entry Name Injection in APK bundle (Zip Slip for zip consumers)
Details

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.

Show details on source website

{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 1.8.2"
      },
      "package": {
        "ecosystem": "Go",
        "name": "github.com/mvt-project/androidqf"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.8.3"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [],
  "database_specific": {
    "cwe_ids": [
      "CWE-22"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-05-21T17:09:00Z",
    "nvd_published_at": null,
    "severity": "LOW"
  },
  "details": "### Summary\n`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.\n\n### Impact\nA compromised device could inject path traversal sequences into the acquisition bundle\u0027s 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.\n\n### Patched version\n[1.8.3](https://github.com/mvt-project/androidqf/releases/tag/v1.8.3)\n\n### Credits\nThis issue was identified during a security assessment conducted by 0xche.",
  "id": "GHSA-jf2q-463c-6f52",
  "modified": "2026-05-21T17:09:00Z",
  "published": "2026-05-21T17:09:00Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/mvt-project/androidqf/security/advisories/GHSA-jf2q-463c-6f52"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/mvt-project/androidqf"
    },
    {
      "type": "WEB",
      "url": "https://github.com/mvt-project/androidqf/releases/tag/v1.8.3"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "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",
      "type": "CVSS_V4"
    }
  ],
  "summary": "androidqf: Zip entry Name Injection in APK bundle (Zip Slip for zip consumers)"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…