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

Integration with other concolic executors #2668

Open
domenukk opened this issue Nov 7, 2024 · 0 comments
Open

Integration with other concolic executors #2668

domenukk opened this issue Nov 7, 2024 · 0 comments

Comments

@domenukk
Copy link
Member

domenukk commented Nov 7, 2024

Hello there.

We have developed a new Rust-native concolic executor that we would like to integrate with libAFL for hybrid fuzzing. Before proceeding, I would like to discuss some considerations regarding the integration of a new concolic executor.

I reviewed the existing implementation for SymCC and noted the following:

  • DSE (concolic execution) is expected to report a trace (set of constraints) from an execution.
  • The stage negates these constraints and solves them to generate diverging inputs.

Thus, the integration will involve generating constraints in libAFL's format, with the rest of the process being handled by the framework.

I have a couple of questions:

  1. Are there plans for other use cases of constraints within the fuzzer? If the primary goal is to find diverging inputs, should the fuzzer manage the solver and constraints, or could it simply receive new diverging inputs from the concolic executor? Additionally, what other valuable constraints, beyond assembly-like boolean expressions, could DSE generate for the fuzzer?

I noticed that the expression definitions are closely tied to Z3/SymCC, and there are some inconsistencies in the design (e.g., calls and returns are not treated as symbolic expressions). Do you see any pending improvements in these areas?

Thanks

Originally posted by @momvart in https://github.com/AFLplusplus/LibAFL/discussions/2666

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

1 participant