Uberwoozle
The public DC32 CTF challenge archive names Uberwoozle as submitter for the Speedometer SAO rock-paper-scissors challenge.
SourceCar Hacking Village at DEF CON 32 · United States · 2024
RP2040 CAN-bus badge with CHV SAO ecosystem
Car Hacking Village's DEF CON 32 badge ecosystem centered on a main RP2040 badge with CAN-network surfaces, four CHV SAO connectors, public board and firmware repositories, public CTF challenge notes, and IOActive's separately documented key-fob badge / SAO build.
People
The public DC32 CTF challenge archive names Uberwoozle as submitter for the Speedometer SAO rock-paper-scissors challenge.
SourceThe public DC32 CTF challenge archive names Red Balloon Security as submitter for the TUF challenges.
SourceThe official CHV page and GitHub organization publish the DEF CON 32 badge lineup, board archive, firmware archive, CTF notes, and SAO specification.
SourceIOActive published the three-part build series for the DEF CON 2024 Car Hacking Village key-fob badge / SAO.
SourceThe public DC32 CTF challenge archive names Rivian as submitter for several vehicle-network challenges.
SourceIt adds the automotive-security village line to the worldwide compendium: the badge acted as a hands-on CAN lab, a platform for SAO peripherals, and a CTF target where attendees could enumerate vehicle-like traffic, inspect the board, use UART, and interact with speedometer and key-fob style add-ons.
The official CHV page documents the 2024 main badge, RP2040 controller, four CAN networks, a dry CAN connector, and four SAO connectors. The public board repository preserves KiCad PCB and schematic files, PCBWay BOM material, pick-and-place files, footprints, and plot outputs. The CHV SAO specification replaces the normal SAO I2C pins with CAN TX and CAN RX over a 3.3 V SAO-style connector. IOActive's key-fob series documents a DEF CON 32 CHV key-fob badge / SAO design around a dsPIC33CK32MP502 microcontroller, CAN transceiver, five NeoPixels, touch buttons, IR receiver, 125 kHz RFID receive, and 433 MHz transmit behavior.
The firmware repository describes a car-on-a-board firmware stack for emulating a car on one PCB, with C and Python firmware areas, manufacturer verification material, RP2040 flashing instructions, BootSel/reset workflow, and socketcan/cansniffer support. The public DC32 CTF challenge archive documents main-badge CAN enumeration, random CAN traffic, a UART Python REPL flag path, and a Speedometer SAO rock-paper-scissors challenge, alongside Red Balloon Security and Rivian vehicle-network challenges.
Car Hacking Village's 2024 page listed the main badge, kids badge, Speedometer SAO, key-fob SAO, PRNDL SAO, and other village badge artifacts as limited DEF CON 32 hardware. IOActive's three-part writeup framed the key-fob project as an exclusive DEF CON 2024 Car Hacking Village badge built to fit the CHV CAN SAO ecosystem.
Lifecycle
IOActive's build series documents a key-fob badge / SAO for DEF CON 32 CHV with dsPIC33CK32MP502, CAN transceiver, NeoPixels, touch buttons, IR, 125 kHz RFID receive, and 433 MHz transmit surfaces.
SourceThe public CTF archive ties the Speedometer SAO to rock-paper-scissors behavior, CAN messages, firmware reversing, and LCD output used in the challenge.
SourceThe public Speedometer SAO firmware repository is MIT-licensed and says it includes CTF problem and notes material built on a display library.
SourceThe CHV SAO spec provides 3.3 V and ground while replacing normal SAO I2C with CAN TX and CAN RX for vehicle-network add-ons.
SourceThe public challenge archive documents main-badge CAN enumeration, a physical-inspection flag under the battery pack, random traffic, and a UART Python REPL path.
SourceThe firmware repository describes firmware intended to emulate a car on one PCB, with C and Python areas, verification files, RP2040 flashing workflow, and socketcan/cansniffer output.
SourceThe official CHV page documents the 2024 main badge with an RP2040, four CAN networks, a dry CAN connector, and four SAO connectors, while the public board tree preserves KiCad and production files.
SourceOperational history
The record remains image-free rather than copying event-page images, blog photos, repository images, social previews, screenshots, generated art, or approximate badge artwork.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The catalogue cites those repositories as source evidence but does not treat repository images, board renders, firmware, CTF material, or documentation as broadly reusable publication assets without explicit license coverage.
The compendium keeps the badge under its own village lineage while preserving DEF CON event context and avoiding an attendee-wide DEF CON main-badge claim.