Read the docs
TI-2024-38566 Aliases GHSA-hvp5-5x4f-33fq

JADX file override vulnerability

Priority LOW 38CWE-22Published · Updated

Key facts

Attack vector
—
Privileges required
—
User interaction
—
Attack complexity
—
Impact type
—
Confidentiality · integrity · availability
—
Fix status
Fixed

No CVSS vector from any source. Fix status from GitHub.

Summary

### Summary 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. ```java private String getResAlias(int resRef, String origKeyName, @Nullable FieldNode constField) { ``` but type style will return the original filename directly. ![img](https://quan9i.oss-cn-beijing.aliyuncs.com/img/202401232212491.jpeg) 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 attack_file_sayhiiiiiiiiiiiii, it doesn't matter what the content is! ![img](https://quan9i.oss-cn-beijing.aliyuncs.com/img/202401232212073.jpg) generate an initial APK #### step2 extract this initial APK using ZIP software to get resources.arsc ![img](https://quan9i.oss-cn-beijing.aliyuncs.com/img/202401232212841.jpg) drop resources.arsc into 010editor #### step3 search for the previous filename attack_file_sayhiiiiiiiiiiiii , two will appear here, we choose the second one ![img](https://quan9i.oss-cn-beijing.aliyuncs.com/img/202401232213527.jpg) let's change the name of the file here. I'll change it to ../../_file_sayhiiiiiiiiiiiii note that you can only overwrite files in the folder where the decompile was saved. ![img](https://quan9i.oss-cn-beijing.aliyuncs.com/img/202401232213343.jpg) #### step4 change the type of this file to style ![img](https://quan9i.oss-cn-beijing.aliyuncs.com/img/202401232213183.jpg) modified to 0E ![img](https://quan9i.oss-cn-beijing.aliyuncs.com/img/202401232213484.jpg) #### step5 After saving, re-compress the whole folder into a zip, then change the extension to APK. open it with JADX and you can see that it has been changed to a style type. ![img](https://quan9i.oss-cn-beijing.aliyuncs.com/img/202401232213864.jpg) click save all ![img](https://quan9i.oss-cn-beijing.aliyuncs.com/img/202401232213119.jpg) you can see the file escaping. ![img](https://quan9i.oss-cn-beijing.aliyuncs.com/img/202401232213746.jpg) so we can also construct a ![img](https://quan9i.oss-cn-beijing.aliyuncs.com/img/202401232213497.jpg) so the classes.dex file is also replaced here ![img](https://quan9i.oss-cn-beijing.aliyuncs.com/img/202401232213075.jpg) ### PoC the details above have been written ### Impact latest version

Why it matters now

Fix Fixed io.github.skylot:jadx-core (Maven): 1.5.0

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—io.github.skylot:jadx-core (Maven)before 1.5.01.5.0Patch availableGHSA-hvp5-5x4f-33fq
  • io.github.skylot:jadx-core (Maven) Vendor— Affected before 1.5.0 Fixed in 1.5.0 Patch available GHSA-hvp5-5x4f-33fq

Remediation

  • Fix · GHSA-hvp5-5x4f-33fq io.github.skylot:jadx-core (Maven) Fixed in 1.5.0 Advisory →

Timeline

  1. 2026-10-03 Threatist record created from GHSA-hvp5-5x4f-33fq

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences