Related Papers

[reach-the-peak]

Hello, I would like to ask if there is a corresponding paper for this project, if so, please recommend me, thank you

[JordanSamhi]

Hi @reach-the-peak ,

Yes, the corresponding paper is: https://dl.acm.org/doi/abs/10.1145/3510003.3512766

pdf: https://www.jordansamhi.com/files/papers/jucify.pdf

[reach-the-peak]

Thank you so much

[reach-the-peak]

Why is the field content such as invokee_method not generated?[]

[JordanSamhi]

This is highly dependent on the symbolic execution, how long did you have it run?
If it is not able to gather enough information to map a native method to the native function, it will not generate it.

[reach-the-peak]

It took about 30 to 40 minutes to run, using the main.sh in the scripts to run, until the end of the program running, I found that it consumed a lot of memory during the running process, my computer has 16G memory, does the configuration of the computer affect symbolic execution? , or is it related to the size of the apk, my apk contains many .so filessymbolic execution

[reach-the-peak]

This is the generated result file, not completely generated

[JordanSamhi]

Hi, yes symbolic execution consumes a lot of memory, I would say that 16Go is not enough for big apps that is for sure.
I usually use servers with 600Go of memory for the experiments like that.
So if you have several so file this is normal that it takes some time.
Also, it depends how were the so files compiled.

[reach-the-peak]

ok i got it thank you

[reach-the-peak]

Hello, I have tested Jucify for analyzing large APK files on a 1T cloud server platform. The size of the APK files tested were under 100M, but the results were not satisfactory. I found that the issue was with the nativediscloser module, which did not analyze many of the SO files properly and failed to generate necessary result files such as .result and .entrypoint files. Even the performance statistics files were not generated. Can you please explain why this is happening and whether it is related to the compilation method of the SO files? I would appreciate it if you could provide a detailed explanation. Thank you. | | syh18655748115 | | ***@***.*** | ---- Replied Message ---- | From | Jordan ***@***.***> | | Date | 3/3/2023 19:47 | | To | ***@***.***> | | Cc | ***@***.***> , ***@***.***> | | Subject | Re: [JordanSamhi/JuCify] Related Papers (Issue #10) | Hi, yes symbolic execution consumes a lot of memory, I would say that 16Go is not enough for big apps that is for sure. I usually use servers with 600Go of memory for the experiments like that. So if you have several so file this is normal that it takes some time. Also, it depends how were the so files compiled. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[JordanSamhi]

Hi @reach-the-peak,

I believe that nativediscloser did not analyze some of the so files since it was stuck analyzing one of them during the symbolic execution. I am not a 100% sure but my guess would be that this is the problem. You can modify the scripts to add a timeout for the symbolic execution of so files if you want, that could help.