home.social

#aflplusplus — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #aflplusplus, aggregated by home.social.

  1. LibAFL 0.15.4 has just been released 🎉

    Of the 30 Contributers for this release, almost half are new faces <3

    github.com/AFLplusplus/LibAFL/

    #Fuzzing #LibAFL #AFLplusplus

  2. LibAFL 0.15.4 has just been released 🎉

    Of the 30 Contributers for this release, almost half are new faces <3

    github.com/AFLplusplus/LibAFL/

    #Fuzzing #LibAFL #AFLplusplus

  3. LibAFL 0.15.4 has just been released 🎉

    Of the 30 Contributers for this release, almost half are new faces <3

    github.com/AFLplusplus/LibAFL/

    #Fuzzing #LibAFL #AFLplusplus

  4. LibAFL 0.15.4 has just been released 🎉

    Of the 30 Contributers for this release, almost half are new faces <3

    github.com/AFLplusplus/LibAFL/

    #Fuzzing #LibAFL #AFLplusplus

  5. LibAFL 0.15.4 has just been released 🎉

    Of the 30 Contributers for this release, almost half are new faces <3

    github.com/AFLplusplus/LibAFL/

    #Fuzzing #LibAFL #AFLplusplus

  6. Want to learn how to build your own #libafl components, but never had the right project? Try working through the interactive exercises that I released today: https://github.com/addisoncrump/parking-game-fuzzer

    You'll work through building your own LibAFL components with templates, allowing you to understand them progressively through the context of trying to solve "Tokyo Parking" (AKA Thinkfun's "Rush Hour") puzzles with fuzzing.

    #fuzzing #aflplusplus #puzzles #rust #rustlang

  7. Want to learn how to build your own #libafl components, but never had the right project? Try working through the interactive exercises that I released today: https://github.com/addisoncrump/parking-game-fuzzer

    You'll work through building your own LibAFL components with templates, allowing you to understand them progressively through the context of trying to solve "Tokyo Parking" (AKA Thinkfun's "Rush Hour") puzzles with fuzzing.

    #fuzzing #aflplusplus #puzzles #rust #rustlang

  8. Want to learn how to build your own #libafl components, but never had the right project? Try working through the interactive exercises that I released today: https://github.com/addisoncrump/parking-game-fuzzer

    You'll work through building your own LibAFL components with templates, allowing you to understand them progressively through the context of trying to solve "Tokyo Parking" (AKA Thinkfun's "Rush Hour") puzzles with fuzzing.

    #fuzzing #aflplusplus #puzzles #rust #rustlang

  9. Want to learn how to build your own #libafl components, but never had the right project? Try working through the interactive exercises that I released today: https://github.com/addisoncrump/parking-game-fuzzer

    You'll work through building your own LibAFL components with templates, allowing you to understand them progressively through the context of trying to solve "Tokyo Parking" (AKA Thinkfun's "Rush Hour") puzzles with fuzzing.

    #fuzzing #aflplusplus #puzzles #rust #rustlang

  10. Want to learn how to build your own #libafl components, but never had the right project? Try working through the interactive exercises that I released today: https://github.com/addisoncrump/parking-game-fuzzer

    You'll work through building your own LibAFL components with templates, allowing you to understand them progressively through the context of trying to solve "Tokyo Parking" (AKA Thinkfun's "Rush Hour") puzzles with fuzzing.

    #fuzzing #aflplusplus #puzzles #rust #rustlang

  11. Guess who just released #LibAFL 0.15.3?
    That's right, you all did! (thank you☺️)

    Highlights:

    • better forkserver
    • scriptable Lua mutations
    • SIMD performance in stable rust
    • CmpLog and RISC-V for LibAFL_Unicorn
    • TMin for LibAFL_QEMU
    • Updated Sugar for easy fuzzing

    github.com/AFLplusplus/LibAFL/

    #fuzzing #AFLplusplus #LibAFL #update

  12. Guess who just released #LibAFL 0.15.3?
    That's right, you all did! (thank you☺️)

    Highlights:

    • better forkserver
    • scriptable Lua mutations
    • SIMD performance in stable rust
    • CmpLog and RISC-V for LibAFL_Unicorn
    • TMin for LibAFL_QEMU
    • Updated Sugar for easy fuzzing

    github.com/AFLplusplus/LibAFL/

    #fuzzing #AFLplusplus #LibAFL #update

  13. Guess who just released #LibAFL 0.15.3?
    That's right, you all did! (thank you☺️)

    Highlights:

    • better forkserver
    • scriptable Lua mutations
    • SIMD performance in stable rust
    • CmpLog and RISC-V for LibAFL_Unicorn
    • TMin for LibAFL_QEMU
    • Updated Sugar for easy fuzzing

    github.com/AFLplusplus/LibAFL/

    #fuzzing #AFLplusplus #LibAFL #update

  14. Guess who just released #LibAFL 0.15.3?
    That's right, you all did! (thank you☺️)

    Highlights:

    • better forkserver
    • scriptable Lua mutations
    • SIMD performance in stable rust
    • CmpLog and RISC-V for LibAFL_Unicorn
    • TMin for LibAFL_QEMU
    • Updated Sugar for easy fuzzing

    github.com/AFLplusplus/LibAFL/

    #fuzzing #AFLplusplus #LibAFL #update

  15. Guess who just released #LibAFL 0.15.3?
    That's right, you all did! (thank you☺️)

    Highlights:

    • better forkserver
    • scriptable Lua mutations
    • SIMD performance in stable rust
    • CmpLog and RISC-V for LibAFL_Unicorn
    • TMin for LibAFL_QEMU
    • Updated Sugar for easy fuzzing

    github.com/AFLplusplus/LibAFL/

    #fuzzing #AFLplusplus #LibAFL #update

  16. 🚨 LibAFL 0.15.2 🚨

    • Rust 2024 edition
    • LibAFL_Unicorn
    • Use LibAFL rand types for other crates
    • Allow logging to StatsD
    • LibAFL_QEMU updates like binary-only ASan in Rust 🦀🦀🦀, inputs via StdIn, better snapshots

    And so much more:

    github.com/AFLplusplus/LibAFL/

    #LibAFL #Fuzzing #AFLplusplus

  17. 🚨 LibAFL 0.15.2 🚨

    • Rust 2024 edition
    • LibAFL_Unicorn
    • Use LibAFL rand types for other crates
    • Allow logging to StatsD
    • LibAFL_QEMU updates like binary-only ASan in Rust 🦀🦀🦀, inputs via StdIn, better snapshots

    And so much more:

    github.com/AFLplusplus/LibAFL/

    #LibAFL #Fuzzing #AFLplusplus

  18. 🚨 LibAFL 0.15.2 🚨

    • Rust 2024 edition
    • LibAFL_Unicorn
    • Use LibAFL rand types for other crates
    • Allow logging to StatsD
    • LibAFL_QEMU updates like binary-only ASan in Rust 🦀🦀🦀, inputs via StdIn, better snapshots

    And so much more:

    github.com/AFLplusplus/LibAFL/

    #LibAFL #Fuzzing #AFLplusplus

  19. 🚨 LibAFL 0.15.2 🚨

    • Rust 2024 edition
    • LibAFL_Unicorn
    • Use LibAFL rand types for other crates
    • Allow logging to StatsD
    • LibAFL_QEMU updates like binary-only ASan in Rust 🦀🦀🦀, inputs via StdIn, better snapshots

    And so much more:

    github.com/AFLplusplus/LibAFL/

    #LibAFL #Fuzzing #AFLplusplus

  20. 🚨 LibAFL 0.15.2 🚨

    • Rust 2024 edition
    • LibAFL_Unicorn
    • Use LibAFL rand types for other crates
    • Allow logging to StatsD
    • LibAFL_QEMU updates like binary-only ASan in Rust 🦀🦀🦀, inputs via StdIn, better snapshots

    And so much more:

    github.com/AFLplusplus/LibAFL/

    #LibAFL #Fuzzing #AFLplusplus

  21. is there a simple way to have the target binary dump it's own test-case while running from afl-fuzz #aflplusplus #afl++ - the thing is, the target binary generates some crypto keys at the start which are used later. i thought to have persistent mode first generate the internal state, then dump the message that is basis for fuzzing and that later in processing needs those keys. but when i run afl-fuzz it complains that the input directory is empty, and when i write the file it's not picked up...

  22. is there a simple way to have the target binary dump it's own test-case while running from afl-fuzz #aflplusplus #afl++ - the thing is, the target binary generates some crypto keys at the start which are used later. i thought to have persistent mode first generate the internal state, then dump the message that is basis for fuzzing and that later in processing needs those keys. but when i run afl-fuzz it complains that the input directory is empty, and when i write the file it's not picked up...

  23. is there a simple way to have the target binary dump it's own test-case while running from afl-fuzz #aflplusplus #afl++ - the thing is, the target binary generates some crypto keys at the start which are used later. i thought to have persistent mode first generate the internal state, then dump the message that is basis for fuzzing and that later in processing needs those keys. but when i run afl-fuzz it complains that the input directory is empty, and when i write the file it's not picked up...

  24. Late last year we released #LibAFL 0.11.2
    Highlights:

    • Unicode-preserving mutators, better mutations for text!
    • GSoC project: Nicer TUI
    • Scalability introspector
    • Improved libafl_frida
    • Extended libafl_qemu - added CmpLog and more!

    Full changelog:
    github.com/AFLplusplus/LibAFL/

    #fuzzing #libafl #AFLplusplus

  25. Late last year we released #LibAFL 0.11.2
    Highlights:

    • Unicode-preserving mutators, better mutations for text!
    • GSoC project: Nicer TUI
    • Scalability introspector
    • Improved libafl_frida
    • Extended libafl_qemu - added CmpLog and more!

    Full changelog:
    github.com/AFLplusplus/LibAFL/

    #fuzzing #libafl #AFLplusplus

  26. Late last year we released #LibAFL 0.11.2
    Highlights:

    • Unicode-preserving mutators, better mutations for text!
    • GSoC project: Nicer TUI
    • Scalability introspector
    • Improved libafl_frida
    • Extended libafl_qemu - added CmpLog and more!

    Full changelog:
    github.com/AFLplusplus/LibAFL/

    #fuzzing #libafl #AFLplusplus

  27. Late last year we released #LibAFL 0.11.2
    Highlights:

    • Unicode-preserving mutators, better mutations for text!
    • GSoC project: Nicer TUI
    • Scalability introspector
    • Improved libafl_frida
    • Extended libafl_qemu - added CmpLog and more!

    Full changelog:
    github.com/AFLplusplus/LibAFL/

    #fuzzing #libafl #AFLplusplus

  28. Late last year we released #LibAFL 0.11.2
    Highlights:

    • Unicode-preserving mutators, better mutations for text!
    • GSoC project: Nicer TUI
    • Scalability introspector
    • Improved libafl_frida
    • Extended libafl_qemu - added CmpLog and more!

    Full changelog:
    github.com/AFLplusplus/LibAFL/

    #fuzzing #libafl #AFLplusplus

  29. If you want to play with the injection vulnerability detection feature shown at #37c3: for AFL++ read instrumentation/README.injections.md; for libafl_qemu check out the vhqemu branch and use fuzzers/qemu_launcher with "-y injections.yaml". #aflplusplus #afl #fuzzing #fuzzing-tools

  30. If you want to play with the injection vulnerability detection feature shown at #37c3: for AFL++ read instrumentation/README.injections.md; for libafl_qemu check out the vhqemu branch and use fuzzers/qemu_launcher with "-y injections.yaml". #aflplusplus #afl #fuzzing #fuzzing-tools

  31. If you want to play with the injection vulnerability detection feature shown at #37c3: for AFL++ read instrumentation/README.injections.md; for libafl_qemu check out the vhqemu branch and use fuzzers/qemu_launcher with "-y injections.yaml". #aflplusplus #afl #fuzzing #fuzzing-tools

  32. If you want to play with the injection vulnerability detection feature shown at #37c3: for AFL++ read instrumentation/README.injections.md; for libafl_qemu check out the vhqemu branch and use fuzzers/qemu_launcher with "-y injections.yaml". #aflplusplus #afl #fuzzing #fuzzing-tools

  33. If you want to play with the injection vulnerability detection feature shown at #37c3: for AFL++ read instrumentation/README.injections.md; for libafl_qemu check out the vhqemu branch and use fuzzers/qemu_launcher with "-y injections.yaml". #aflplusplus #afl #fuzzing #fuzzing-tools

  34. Almost a year after my defense, my PhD thesis "Automated Security Testing of Unexplored Targets Through Feedback-Guided Fuzzing" is now archived on the university server. 🎉
    We fuzzed Nvidia drivers, tcp servers, basebands, WebAssembly,...

    Enjoy reading :)

    depositonce.tu-berlin.de/items

    #fuzzing #AFLplusplus

  35. Almost a year after my defense, my PhD thesis "Automated Security Testing of Unexplored Targets Through Feedback-Guided Fuzzing" is now archived on the university server. 🎉
    We fuzzed Nvidia drivers, tcp servers, basebands, WebAssembly,...

    Enjoy reading :)

    depositonce.tu-berlin.de/items

    #fuzzing #AFLplusplus

  36. Almost a year after my defense, my PhD thesis "Automated Security Testing of Unexplored Targets Through Feedback-Guided Fuzzing" is now archived on the university server. 🎉
    We fuzzed Nvidia drivers, tcp servers, basebands, WebAssembly,...

    Enjoy reading :)

    depositonce.tu-berlin.de/items

    #fuzzing #AFLplusplus

  37. Almost a year after my defense, my PhD thesis "Automated Security Testing of Unexplored Targets Through Feedback-Guided Fuzzing" is now archived on the university server. 🎉
    We fuzzed Nvidia drivers, tcp servers, basebands, WebAssembly,...

    Enjoy reading :)

    depositonce.tu-berlin.de/items

    #fuzzing #AFLplusplus

  38. Almost a year after my defense, my PhD thesis "Automated Security Testing of Unexplored Targets Through Feedback-Guided Fuzzing" is now archived on the university server. 🎉
    We fuzzed Nvidia drivers, tcp servers, basebands, WebAssembly,...

    Enjoy reading :)

    depositonce.tu-berlin.de/items

    #fuzzing #AFLplusplus

  39. Finally came around to do some #fuzzing on #sectxtlib with #AFLplusplus and directly found an issue in one of its dependencies 🔥​

  40. Finally came around to do some #fuzzing on #sectxtlib with #AFLplusplus and directly found an issue in one of its dependencies 🔥​

  41. Finally came around to do some #fuzzing on #sectxtlib with #AFLplusplus and directly found an issue in one of its dependencies 🔥​

  42. Finally came around to do some #fuzzing on #sectxtlib with #AFLplusplus and directly found an issue in one of its dependencies 🔥​

  43. Finally came around to do some #fuzzing on #sectxtlib with #AFLplusplus and directly found an issue in one of its dependencies 🔥​

  44. LibAFL 0.9.0 is out with a new logo🔥

    Highlights:
    → QEMU user-mode and system-mode snapshot fuzzing
    → Stable CorpusId when removing/updating entries in Corpus
    → Tinyinst binary-only instrumentation
    → Full support to AFL++ binaries with forkserver
    ...

    github.com/AFLplusplus/LibAFL/

    #fuzzing #libafl #AFLplusplus

  45. LibAFL 0.9.0 is out with a new logo🔥

    Highlights:
    → QEMU user-mode and system-mode snapshot fuzzing
    → Stable CorpusId when removing/updating entries in Corpus
    → Tinyinst binary-only instrumentation
    → Full support to AFL++ binaries with forkserver
    ...

    github.com/AFLplusplus/LibAFL/

    #fuzzing #libafl #AFLplusplus

  46. LibAFL 0.9.0 is out with a new logo🔥

    Highlights:
    → QEMU user-mode and system-mode snapshot fuzzing
    → Stable CorpusId when removing/updating entries in Corpus
    → Tinyinst binary-only instrumentation
    → Full support to AFL++ binaries with forkserver
    ...

    github.com/AFLplusplus/LibAFL/

    #fuzzing #libafl #AFLplusplus

  47. LibAFL 0.9.0 is out with a new logo🔥

    Highlights:
    → QEMU user-mode and system-mode snapshot fuzzing
    → Stable CorpusId when removing/updating entries in Corpus
    → Tinyinst binary-only instrumentation
    → Full support to AFL++ binaries with forkserver
    ...

    github.com/AFLplusplus/LibAFL/

    #fuzzing #libafl #AFLplusplus

  48. LibAFL 0.9.0 is out with a new logo🔥

    Highlights:
    → QEMU user-mode and system-mode snapshot fuzzing
    → Stable CorpusId when removing/updating entries in Corpus
    → Tinyinst binary-only instrumentation
    → Full support to AFL++ binaries with forkserver
    ...

    github.com/AFLplusplus/LibAFL/

    #fuzzing #libafl #AFLplusplus

  49. For binary-only emulation in #LibAFL qemu, you can now dump DrCov traces to see in #idapro (lighthouse), #binaryninja (bncov), or #ghidra (dragondance) which paths the executions took.

    This helps you understand where your fuzzer gets stuck, develop the harness further, and reach greater depth in the binary, eventually.

    Binary-only modes of #AFLplusplus ( #qemu / #frida ) and libafl_frida also support DrCov output, already.

    #fuzzing #fuzzingTips
    github.com/AFLplusplus/LibAFL/

  50. For binary-only emulation in #LibAFL qemu, you can now dump DrCov traces to see in #idapro (lighthouse), #binaryninja (bncov), or #ghidra (dragondance) which paths the executions took.

    This helps you understand where your fuzzer gets stuck, develop the harness further, and reach greater depth in the binary, eventually.

    Binary-only modes of #AFLplusplus ( #qemu / #frida ) and libafl_frida also support DrCov output, already.

    #fuzzing #fuzzingTips
    github.com/AFLplusplus/LibAFL/