Lib.rs

› Development tools › Testing | Embedded development | Operating systems › LibAFL
#shared-memory #security-testing #fuzzing #security

no-std libafl_bolts

Low-level bolts to create fuzzers and so much more

by Andrea Fioraldi, Dominik Maier and 97 contributors. Owned by AFLplusplus.

7 releases

0.13.2 Jul 31, 2024
0.13.1 Jun 30, 2024
0.12.0 Apr 12, 2024
0.11.2 Dec 21, 2023
0.11.1 Aug 31, 2023

#440 in Testing

Download history 491/week @ 2024-07-08 346/week @ 2024-07-15 101/week @ 2024-07-22 307/week @ 2024-07-29 217/week @ 2024-08-05 55/week @ 2024-08-12 61/week @ 2024-08-19 112/week @ 2024-08-26 108/week @ 2024-09-02 165/week @ 2024-09-09 248/week @ 2024-09-16 214/week @ 2024-09-23 131/week @ 2024-09-30 142/week @ 2024-10-07 176/week @ 2024-10-14 148/week @ 2024-10-21

607 downloads per month
Used in 8 crates

MIT/Apache

560KB
12K SLoC

LibAFL_bolts: OS and Fuzzer Dev's Libary Collection.

LibAFL logo

The libafl_bolts crate exposes a lot of low-level features of LibAFL for projects that are unrelated to fuzzing, or just fuzzers completely different to LibAFL. Some cross-platform things in bolts include (but are not limited to):

  • SerdeAnyMap: a map that stores and retrieves elements by type and is serializable and deserializable
  • ShMem: A cross-platform (Windows, Linux, Android, MacOS) shared memory implementation
  • LLMP: A fast, lock-free IPC mechanism via SharedMap
  • Core_affinity: A maintained version of core_affinity that can be used to get core information and bind processes to cores
  • Rands: Fast random number generators for fuzzing (like RomuRand)
  • MiniBSOD: get and print information about the current process state including important registers.
  • Tuples: Haskel-like compile-time tuple lists
  • Os: OS specific stuff like signal handling, windows exception handling, pipes, and helpers for fork

LibAFL_bolts is written and maintained by

Contributing

For bugs, feel free to open issues or contact us directly. Thank you for your support. <3

Even though we will gladly assist you in finishing up your PR, try to

  • keep all the crates compiling with stable rust (hide the eventual non-stable code under cfgs)
  • run cargo nightly fmt on your code before pushing
  • check the output of cargo clippy --all or ./clippy.sh
  • run cargo build --no-default-features to check for no_std compatibility (and possibly add #[cfg(feature = "std")]) to hide parts of your code.

Some of the parts in this list may be hard, don't be afraid to open a PR if you cannot fix them by yourself, so we can help.

License

Licensed under either of Apache License, Version 2.0 or MIT license at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in this crate by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.
Dependencies under more restrictive licenses, such as GPL or AGPL, can be enabled using the respective feature in each crate when it is present, such as the 'agpl' feature of the libafl crate.

Dependencies

~0.5–42MB
~671K SLoC