meetings

We will cover the high-level concept of a fuzzer, then dig into the paper written by the authors of LibAFL, and then explore some code.

From the GitHub page: “LibAFL is a collection of reusable pieces of fuzzers, written in Rust. It is fast, multi-platform, no_std compatible, and scales over cores and machines.”

If you want to learn and explore in advance, here are the main resources:

GitHub is here: https://github.com/AFLplusplus/LibAFL

Academic paper is here: https://www.s3.eurecom.fr/docs/ccs22_fioraldi.pdf

Bring the invisible world of Bluetooth communications to light using the newly released ‘Bluetooth Demystifier’, from Lost Rabbit Labs https://gitlab.com/lost-rabbit-labs. This freely available, open-source software package allows you to examine and explore the Bluetooth/BLE landscape around you. The Lost Rabbit Labs team will demonstrate how to use ‘Bluetooth Demystifier’, provide the software for all to use, and manage a small CTF around detecting a rogue signal (potential malicious BT device).

Attendees do not have to bring anything as we will be mostly demoing our soon-to-be-released open-source software (projected release between April 18th - April 21st) against the Bluetooth devices we are bringing.

However, if attendees do want to participate, there are three options:

Linux OS laptops that support the BlueZ stack (Not ported to Windows yet nor will it run inside a Linux VM)
A laptop + a Raspberry Pi to configure (the Pi will be running the Bluetooth Demystifier software)
Any device with a web browser to view the front-end application from the LAN (Not entirely sure how many attendees can view this data at once due to Pi's resources)

Attendees can install it before hand (via Linux laptop or on a raspberry pi), with our help at the meetup, or can choose to access the front-end side via a device with a web browser during the event.

Let’s discuss the recent remote execution vulnerability in Log4J. To catch us all up to the same base understanding, we will start off with a presentation explaining the root cause and impact of the vulnerability, as well as work through an exercise that demonstrates this vulnerability. Other topics we can discuss include what resources and tooling we’ve found, remediations we’ve seen that either work or don’t work, and how this event affected our day jobs.

@j0nh4t discovered that you can escalate from user to SYSTEM on an unlocked Windows machine just by plugging in a Razer mouse and clicking in the right places. At this meeting we’ll take a look at how the specific exploit works and more interestingly how it falls into a no man’s land where there are probably a lot more bugs to find. We’ll look at how Windows identifies USB devices, decides which driver to install, and then where it downloads the driver from. Armed with that knowledge, we’ll take a ~$5 Digispark Kickstarter Attiny85 board (https://smile.amazon.com/s?k=digispark+kickstarter+attiny85) and emulate a Razer device to trigger the vulnerability. If you bring your own board you can go home with a Windows master key (assuming no patches are released). Please come with the Arduino IDE installed for the full DIY experience.