-
Notifications
You must be signed in to change notification settings - Fork 163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
zergRush not functioning on android 2.3.6 #2
Comments
Might be because of line 137, "void *dlh = dlopen("/system/libc/libc.so", RTLD_NOW);". At least on my Galaxy s2, that file is at "/system/lib/libc.so"... |
Not working for me either. Android 2.3.6, ascend g300. If it failed to open libc on that line it should print... But I changed the binary to /system/lib/libc.so and it didn't work. It should say "[+] Zerglings found a way to enter !..." if it worked. Looks like it's trying to send something to 'vold' to attempt to crash it. 'vold' is the mount tool so they suggest you unmount any sdcards first, but it still didn't work for me. |
I don't think it has anything to do with 2.3.6 per se. It works on my 2.3.6 MTK device. It is possible that there is a specific update that patches this vulnerability or there must be something that can be done with the buffer size. |
hi, how to build this c code...i build it with ndk, but error:
Look forward to your reply. |
@dash17291 thanks! |
Samsung Galaxy Player 70 Plus (YP-GB70D) Running Android 2.3.6
Kernel version: 2.6.35.7 - se.infra@SEP-73 #2
Build number - GINGERBREAD.KRLD2
Here is the output from the adb shell:
$ /data/local/tmp/zergRush
/data/local/tmp/zergRush
[**] Zerg rush - Android 2.2/2.3 local root
** 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00000118
[+] Found a Samsung, running Samsung mode
[] Scooting ...
[] Sleeping a bit (~40s)...
[] Waking !
[] Sending 149 zerglings ...
[] Sleeping a bit (~40s)...
[] Waking !
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
$
Any chance this could be fixed?
The text was updated successfully, but these errors were encountered: