Commands: -1 compress faster -9 compress better -d decompress -l list compressed file -t test compressed file -V display version number -h give more help -L display software license Options: -q be quiet -v be verbose -oFILE write output to 'FILE' -f force compression of suspicious files -k keep backup files file.. executables to (de)compress
Type 'upx.out_x86-64 --help' for more detailed help.
UPX comes with ABSOLUTELY NO WARRANTY; for details visit https://upx.github.io
Input file "crash.upx" is now 19088 bytes, starting strategy "bisect"... Verifying the original input executes successfully... (skip with --noverify) ** Message: This program expected `./test1.sh` to return successfully ** Message: for the original input (i.e. exitcode zero). ** Message: Try it yourself to verify it's working. ** Message: Use a command like: `cat crash.upx | ./test.sh || echo failed`
Input file "crash.upx" is now 19088 bytes, starting strategy "bisect"... Verifying the original input executes successfully... (skip with --noverify) The original input file succeeded after 0.0 seconds. New finalized size: 19088 (depth=2) real=0.0s, user=0.0s, speedup=~-0.0s treesize=6654, height=6376, unproc=0, real=4.4^C user=19.3s, speedup=~14.9s
An application has made an attempt to load the C runtime library without using a manifest. This is an unsupported way to load Visual C++ DLLs. You need to modify your application to build with a manifest. For more information, see the "Visual C++ Libraries as Shared Side-by-Side Assemblies" topic in the product documentation.
微软的链接中也提到了解决的方法
1 2 3 4 5 6
Rebuild your application to include a manifest. Building an application with Visual Studio automatically puts the manifest into the resulting .exe or .dll file. If you are building at the command line, use the mt.exe tool to add the manifest as a resource. Use resource ID 1 if you build an .exe, and resource ID 2 if you build a .dll. For more information, see How to: Embed a Manifest Inside a C/C++ Application.
还是先看看manifest的作用，在msdn网站搜索相关内容，根据《Understanding Manifest Generation for C/C++ Programs》中的内容，manfest.xml可以是一个外部的XML文件也可以是嵌入在程序的资源文件中。manifest.xml用于管理程序在运行时需要的共享程序集的名字和版本。如果程序只依赖 VisualC++ 的程序集（CRT，MFC，ATL等），manifest会被链接器自动生成。Manifest的Sxs指定了其依赖的清单名称,版本,资源,和其他组件。Sxs是Windows XP引入的新技术，vs 2005 开始使用，全名叫Side by Side assembly，主要还是为了解决兼容性问题，这样同一个系统可以存在不同版本的同名文件而互相不影响各自的运行。
Desktop applications can control the location from which a DLL is loaded by specifying a full path, using DLL redirection, or by using a manifest. If none of these methods are used, the system searches for the DLL at load time as described in this section.
.data:080CBB40 daemonname db '!#Ff3VE.-7',17h,'V[_ 0',0 ; DATA XREF: main+31Eo .data:080CBB40 ; main+4AEo ... .data:080CBB40 ; cat resolv.conf .data:080CBB51 align 4 .data:080CBB54 a12 db '1*2',0 ; sh .data:080CBB58 db 0 .data:080CBB59 db 0 .data:080CBB5A db 0 .data:080CBB5B db 0 .data:080CBB5C db 0 .data:080CBB5D db 0 .data:080CBB5E db 0 .data:080CBB5F db 0 .data:080CBB60 db 0 .data:080CBB61 db 0 .data:080CBB62 db 0 .data:080CBB63 db 0 .data:080CBB64 db 0 .data:080CBB65 db 0 .data:080CBB66 db 0 .data:080CBB67 db 0 .data:080CBB68 db 20h ; bash .data:080CBB69 db 23h ; # .data:080CBB6A db 41h ; A .data:080CBB6B db 2Eh ; . .data:080CBB6C db 41h ; A .data:080CBB6D db 0 .data:080CBB6E db 0 .data:080CBB6F db 0 .data:080CBB70 db 0 .data:080CBB71 db 0
...
.data:080CBBB8 db 2Eh ; . ; ls -la .data:080CBBB9 db 31h ; 1 .data:080CBBBA db 12h .data:080CBBBB db 6Bh ; k .data:080CBBBC db 2Dh ; - .data:080CBBBD db 52h ; R .data:080CBBBE db 36h ; 6 .data:080CBBBF db 0 .data:080CBBC0 db 0 .data:080CBBC1 db 0 .data:080CBBC2 db 0 .data:080CBBC3 db 0 .data:080CBBC4 db 0 .data:080CBBC5 db 0 .data:080CBBC6 db 0 .data:080CBBC7 db 0 .data:080CBBC8 db 0 .data:080CBBC9 db 0 .data:080CBBCA db 0 .data:080CBBCB db 0 .data:080CBBCC db 36h ; 6 ; top .data:080CBBCD db 2Dh ; - .data:080CBBCE db 42h ; B .data:080CBBCF db 46h ; F .data:080CBBD0 db 0 .data:080CBBD1 db 0 .data:080CBBD2 db 0
...
呵呵，已经看到 top， ls -al 等信息了，查看daemonname 的交叉引用，发现在main函数 中，到main里看看。
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
.text:0804AC30 ; int __cdecl main(int argc, const char **argv, const char **envp) .text:0804AC30 public main .text:0804AC30 main proc near ; DATA XREF: _start+17o
0067202C - E9 EE9D1900 jmp 0080BE1F 00672031 CC int3 00672032 CC int3 00672033 CC int3 00672034 CC int3 00672035 CC int3 00672036 CC int3 00672037 90 nop
Android安全模型的一个关键部分是每一个应用程序都被赋予一个唯一的 Linux 用户 ID 和组 ID，运行在自己的进程和 Dalvik 虚拟机里。 在应用程序安装的过程中，Android系统设备上创建一个专门的目录（文件夹），用于存储此应用程序的数据，并且仅允许应用程序利用 Linux 用户 ID 和组 ID 的相应访问权限对这些数据进行访问。此外，此应用程序的 Dalvik 虚拟机使用应用程序的用户 ID 运行在自己的进程中。 这些关键的机制在操作系统层面上强制数据安全，因为应用程序之间不共享内存、访问权限及磁盘存储。应用程序只能在它们自己的 Dalvik 虚拟机范围内访问内存和数据。
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
$ ps ...
u0_a16 2757 882 2574956 116944 SyS_epoll+ 0 S com.google.android.gms.persistent u0_a128 2774 883 1939084 87720 SyS_epoll+ 0 S com.ss.android.article.news:push u0_a16 2850 882 2322980 46592 SyS_epoll+ 0 S com.google.process.gapps u0_a128 2887 883 2190568 181868 SyS_epoll+ 0 S com.ss.android.article.news u0_a37 2900 882 2430908 58316 SyS_epoll+ 0 S com.google.android.googlequicksearchbox:interactor nfc 2918 882 2351828 62356 SyS_epoll+ 0 S com.android.nfc u0_a45 2930 882 2309884 43576 SyS_epoll+ 0 S se.dirac.acs radio 2945 882 2313144 45592 SyS_epoll+ 0 S net.oneplus.push u0_a0 2956 882 2304600 36360 SyS_epoll+ 0 S com.oneplus system 2967 882 2307276 38088 SyS_epoll+ 0 S com.fingerprints.serviceext system 2985 882 2309992 42044 SyS_epoll+ 0 S com.oneplus.opbugreportlite u0_a142 2997 882 2370296 93324 SyS_epoll+ 0 S com.oneplus.aod u0_a16 3018 882 2731976 165828 SyS_epoll+ 0 S com.google.android.gms ...
public HashMap<String, List<String>> getBinderCallParameter(String interfaceDescriptor, HashMap<String, Integer> codes) { HashMap<String, List<String>> ret = new HashMap();
if (interfaceDescriptor == null) return ret;
try { Class<?> cStub = Class .forName(interfaceDescriptor + "$Stub$Proxy"); Method[] m = cStub.getDeclaredMethods();
for (Method method : m) { int func_code = 0; List<String> func_parameter = new ArrayList<>();
