Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
3 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
when jadx parses a resource file, there is an escape problem with the style file, which can overwrite other files in the directory when saving the decompile result. Although I don't think this vulnerability realizes path traversal in the true sense of the word , I reported it anyway Details I see that getResAlias does something with the filename. but type style will return the original filename directly. so our goal is to take a malicious file that was originally of type raw, modify its type to style, trick jadx into step1 create an android project using androidstudio and create a raw folder with the name attackfilesayhiiiiiiiiiiiii, it doesn't matter what the content is! generate an initial APK step2 extract this initial APK using ZIP software to get resources.arsc drop resources.arsc into 010editor step3 search for the previous filename attackfilesayhiiiiiiiiiiiii , two will appear here, we choose the second one let's change the name of the file here. I'll change it to…
Recommended action: Upgrade to 1.5.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact Vulnerable library protobuf-java 3.11.4 (CVE-2021-22569) Patches Dependency updated in jadx 1.4.3 References According to the AquaSecurity report: Also, Maven repository have links to this and other vulnerabilities from dependencies: https://mvnrepository.com/artifact/com.google.protobuf/protobuf-java/3.11.4
Recommended action: Upgrade to 1.4.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
skylot/jadx prior to 1.3.2 is vulnerable to Improper Restriction of XML External Entities when a user is tricked into exporting a malicious APK file (via the -e option) containing a crafted AndroidManifest.xml / strings.xml to gradle, leading to possible local file disclosure.
Recommended action: Upgrade to 1.3.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.