problem about finding crashes about winafl HOT 6 CLOSED

test_gdiplus.exe is a real-world target and it's not expected that a crash would be found so quickly. While the test_gdiplus.exe binary is small, it's actually intended to find bugs in gdiplus.dll and WindowsCodecs.dll which are Windows image parsing libraries. Any crash found by it could potentially be an actual vulnerability in Windows OS with security implications.

from winafl.

test_gdiplus.exe is a real-world target and it's not expected that a crash would be found so quickly. While the test_gdiplus.exe binary is small, it's actually intended to find bugs in gdiplus.dll and WindowsCodecs.dll which are Windows image parsing libraries. Any crash found by it could potentially be an actual vulnerability in Windows OS with security implications.

from winafl.

Collaborator

Hold on Ifratric could you give me your contact info? Because I could really use your help and so that we don't take ages to respond, totally up to you tho

from winafl.

And if you don't mind me asking, where does that offset even come from? Like I tried searching for 0x1270 all around in IDA and found nothing in the test_gdiplus.exe

from winafl.

Target offset is the offset of the target function (in examples, usually main, test_target, fuzz or something similar) in memory, starting from the module header. Note that the offset can change every time the target program is recompiled, the exact values given in examples are not guaranteed to be correct.

from winafl.

Target offset is the offset of the target function (in examples, usually main, test_target, fuzz or something similar) in memory, starting from the module header. Note that the offset can change every time the target program is recompiled, the exact values given in examples are not guaranteed to be correct.

But if I run the command with any other offset, I get an error

from winafl.