-
Notifications
You must be signed in to change notification settings - Fork 74
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
Trying to fuzz 7z using Winnie #14
Comments
Hi, could you please post the command line you used? |
afl-fuzz -i in -o out -t 1000 -I 1000 -- -bbfile basicblocks.bb -- -harness harness.dll -no_minidumps -- 7z2106-x64.exe @@ |
Please refer to 7z command line manual: https://sevenzip.osdn.jp/chm/cmdline/syntax.htm
I think the command you want is probably `afl-fuzz -i in -o out -t 1000 -I 1000 -- -bbfile basicblocks.bb -- -harness harness.dll -no_minidumps -- 7z2106-x64.exe x @@`
Since you would normally use 7z like `7z x my_archive.7z` or similar.
…On Wed, Dec 29, 2021 at 08:27, Omkar Bhat ***@***.***> wrote:
afl-fuzz -i in -o out -t 1000 -I 1000 -- -bbfile basicblocks.bb -- -harness harness.dll -no_minidumps -- 7z2106-x64.exe @@
—
Reply to this email directly, [view it on GitHub](#14 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ADR2ESTV6W4TG3UVQDWRBI3UTMLD3ANCNFSM5KVU7LUA).
Triage notifications on the go with GitHub Mobile for [iOS](https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675) or [Android](https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub).
You are receiving this because you commented.Message ID: ***@***.***>
|
I figured out the problem was in harness generation, when I try you Tracer.dll to create a harness I'm getting an error: Failure to map DLL ~\pin\source\tools\Tracer\x64\Release\Tracer.dll. I checked and the dll file is there. Do you know why that maybe be the case. |
It's because you trying to trace 64 bit exe with 32 bit tracer or vice versa. Make sure the .exe and the tracer compiled in the same architecture. |
Can you tell me how to generate the harness(command)? Thank you very much!!! |
I can't remember specifically what I did to successfully generate the harness code. I just followed their tutorial both in home directory and harnessgen folder. |
Thanks |
Have you successfully generated the harness? I encountered a problem: File ".../harness/common.py", line 513, int typedef Have you encountered the similar problem? |
@KB-bit Sorry, I didn't encounter the problem. |
Can you tell me the cmd to generate the harness for toy_example.exe? I followed the tutorial in harnessgen folder , but I failed to generate the harness for toy_example.exe in "../winnie-master/samples/toy_example". |
@KB-bit .\pin.exe -t source/tools/Tracer/Release/Tracer.dll -logdir "cor1_1" -trace_mode "all" -only_to_target "toy_example.exe" -only_to_lib "example_library.dll" -- D:\2022\final\w2\winnie\samples\toy_example\Release\toy_example.exe D:\2022\final\w2\winnie\samples\toy_example\in\input |
Thank you so much : ) |
@KB-bit Hello, have you figured it out? If so, can you share the result with me? |
Hello @KB-bit and @mineechor, I am writing to ask for your help with a similar issue that I'm facing. After running the command Traceback (most recent call last): |
hello, I meet this problem when I use the following command And solve this problem when append "-sample path\input" as you say :) but I don't see the argument of "-sample" in https://github.com/sslab-gatech/winnie/tree/master/harnessgen#one-trace |
maybe you can try $ python3 synthesizer.py harness -t drltrace.PID.log -d memdump -s "test" -sample input if you still paying attention to this paper :) |
Thank you @kirito999 ! I'll try this out. |
I'm new to fuzzing and was trying to understand how your fuzzer works. When I try to Fuzz the 7z (trying to recreate on of the applications mentioned in the paper and I'm getting this error. Can you help me with it?
Also what did you put in the in folder? I tried using a location and a file I know exists should I be doing something else?
The text was updated successfully, but these errors were encountered: