Skip to content
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

Hooked JavaScript parseFloat() to grinder_logger.dll via proxy @ 0x001A000 #71

Open
themrzmaster opened this issue Feb 7, 2017 · 1 comment

Comments

@themrzmaster
Copy link

Hey,

everytime i try running grinder on chrome i cant get the node running and it keeps crashing the browser before the fuzzing proccess.

any ideas?

[+G+] Starting at 2017-02-07 17:52:06
[+G+] Using the config file 'config.rb'...
[+G+] Bringing up Grinder node 'G1' with ruby 2.0.0 (64-bit)...
[+G+] Started the Grinder continue process 4808
[+S+] Starting at 2017-02-07 17:52:06
[+S+] Adding fuzzer 'SimpleExample' to the testcase server
[+S+] Testcase server running on 127.0.0.1:8080
[+G+] Started the Grinder server process 3432
[+G+] Started the Grinder debugger process 3176
[+D+] Starting at 2017-02-07 17:52:09
[+D+] Using the symbol path 'SRVC:\symbols*http://msdl.microsoft.com/download/
symbols;SRV
C:\symbols*http://chromium-browser-symsrv.commondatastorage.googlea
pis.com'.
[+D+] Running 'C:\Program Files (x86)\Google\Chrome\Application\chrome.exe'
[+D+] Attached debugger to new 32-bit process 4200.
[+D+] Debug message from process 4200: RecursiveDirectoryCreate( C:\Users\themrz
master\AppData\Local\Google\Chrome\User Data directory exists )

[+D+] Attached debugger to new 32-bit process 4368.
[+D+] Logger DLL loaded into process 4368 @ 0x73CF0000
[+D+] Logging process 4368 to log file 'C:\Users\themrzmaster\AppData\Local\Temp
\Low\logger_4368.xml'
[+D+] Logger DLL loaded into process 4200 @ 0x73CF0000
[+D+] Logging process 4200 to log file 'C:\Users\themrzmaster\AppData\Local\Temp
\Low\logger_4200.xml'
[+D+] chrome.dll DLL loaded into process 4200 at address 0x0F8B0000
[+D+] Resolved chrome.dll!v8::internal::Runtime_StringParseFloat @ 0x0FF42DA0
[+D+] Hooked JavaScript parseFloat() to grinder_logger.dll via proxy @ 0x001C000
0
[+D+] Attached debugger to new 32-bit process 2180.
[+D+] Attached debugger to new 32-bit process 4864.
[+D+] chrome_child.dll DLL loaded into process 4864 at address 0x0FA90000
[-D-] Unable to hook JavaScript parseFloat() in process 4864, grinder_logger.dll
not injected.
[+D+] chrome_child.dll DLL loaded into process 4864 at address 0x0FA90000
[-D-] Unable to hook JavaScript parseFloat() in process 4864, grinder_logger.dll
not injected.
[+D+] chrome_child.dll DLL loaded into process 4864 at address 0x0FA90000
[-D-] Unable to hook JavaScript parseFloat() in process 4864, grinder_logger.dll
not injected.
[+D+] Logger DLL loaded into process 4864 @ 0x73CF0000
[+D+] Logging process 4864 to log file 'C:\Users\themrzmaster\AppData\Local\Temp
\Low\logger_4864.xml'
[+D+] chrome_child.dll DLL loaded into process 4864 at address 0x0FA90000
[+D+] Resolved chrome_child.dll!v8::internal::Runtime_StringParseFloat @ 0x1014E
2A7
[+D+] Hooked JavaScript parseFloat() to grinder_logger.dll via proxy @ 0x001A000
0
[+D+] Attached debugger to new 32-bit process 6544.
[+D+] Attached debugger to new 32-bit process 1332.
[+D+] chrome_child.dll DLL loaded into process 6544 at address 0x02640000
[-D-] Unable to hook JavaScript parseFloat() in process 6544, grinder_logger.dll
not injected.
[+D+] chrome_child.dll DLL loaded into process 6544 at address 0x02640000
[-D-] Unable to hook JavaScript parseFloat() in process 6544, grinder_logger.dll
not injected.
[+D+] chrome_child.dll DLL loaded into process 6544 at address 0x02640000
[-D-] Unable to hook JavaScript parseFloat() in process 6544, grinder_logger.dll
not injected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants