CyberRota Analysis
AI-GeneratedVersions 1.5.2 to 1.5.5 of the jadx Java decompiler are vulnerable to arbitrary file write due to improper handling of malicious .xapk files, allowing attackers to execute arbitrary code by placing a JAR file in the plugins/dropins directory. This vulnerability poses a significant risk, particularly for users who run jadx from directories that are ancestors of the config directory, as it can lead to the execution of attacker-controlled plugins. Organizations using affected versions should prioritize upgrading to version 1.5.6 to mitigate this high-severity risk.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
jadx is a Dex to Java decompiler. From 1.5.2 to 1.5.5, a malicious .xapk file can cause jadx to write attacker-controlled archive entry contents outside the intended XAPK plugin temporary unpack directory because XApkLoader resolves each entry name directly with tmpDir.resolve(fileName) after a CWD-based ZIP security check. When jadx is launched from a directory that is an ancestor of the config directory, the arbitrary write can plant a JAR in plugins/dropins, and the next jadx run loads the JAR with URLClassLoader and ServiceLoader, executing attacker-controlled plugin code. This issue is fixed in version 1.5.6.