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

Casr doesn't find crashes from vanilla afl output directory results #239

Closed
dumprop opened this issue Feb 5, 2025 · 4 comments · Fixed by #240
Closed

Casr doesn't find crashes from vanilla afl output directory results #239

dumprop opened this issue Feb 5, 2025 · 4 comments · Fixed by #240
Labels
enhancement New feature or request

Comments

@dumprop
Copy link

dumprop commented Feb 5, 2025

I did fuzzing test via SharpFuzz + vanilla AFL
Actual result:

Image

After I made default directory in copy of previous directory (such structure in AFL++) and all goes well:

Image

So, seems that casr doesn't work with output directory structure of vanilla AFL

@SweetVishnya SweetVishnya linked a pull request Feb 6, 2025 that will close this issue
@SweetVishnya SweetVishnya added the enhancement New feature or request label Feb 6, 2025
@SweetVishnya
Copy link
Collaborator

@dumprop, the fix is merged to master. Can you verify, please?

@dumprop
Copy link
Author

dumprop commented Feb 10, 2025

@dumprop, the fix is merged to master. Can you verify, please?

Yes, everything is working now. Thanks for the quick fix.

@headshog
Copy link
Contributor

@dumprop, the fix is merged to master. Can you verify, please?

Yes, everything is working now. Thanks for the quick fix.

Also, if you run C# target with binary (like ./SerializeObject), you'd better use --hint csharp option

@dumprop
Copy link
Author

dumprop commented Feb 10, 2025

@dumprop, the fix is merged to master. Can you verify, please?

Yes, everything is working now. Thanks for the quick fix.

Also, if you run C# target with binary (like ./SerializeObject), you'd better use --hint csharp option

Thanks! Fortunately, all works well without this option in my case.
Maybe it should be mention on documentation?
I afraid I can forget it when it would help

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

Successfully merging a pull request may close this issue.

3 participants