Guide

Getting started: install the tools and practise

The site's hands-on companion. We bring up a virtual CAN bus in two minutes, install the real automotive intrusion-testing tools, and learn to use them on concrete examples. Everything happens on your bench, without ever touching a vehicle.

A virtual bus in two minutes

Before any hardware, Linux can simulate a complete CAN bus in memory. This is SocketCAN, built into the kernel: a vcan interface behaves exactly like a real bus, but nothing leaves the machine. It is the ideal sandbox for learning without risk.

Create a virtual CAN interface vcan0
sudo modprobe vcan
sudo ip link add dev vcan0 type vcan
sudo ip link set up vcan0

# check
ip -details link show vcan0

can-utils: the basic toolbox

can-utils is the reference toolkit, maintained by the linux-can project. Sniff, send, generate, record and replay frames: it all starts here. It is in the repositories of most distributions.

Install can-utils
# Debian, Ubuntu
sudo apt-get install can-utils

# or from source
git clone https://github.com/linux-can/can-utils
cd can-utils && make
candump
Shows every frame going by, live. The tool you leave running all the time.
cansend
Sends a single frame, with the identifier and bytes picked by hand.
cangen
Generates traffic, random or timed, to populate the bus or to fuzz it.
cansniffer
A view that shows only the bytes that change: perfect for spotting a signal.
canplayer
Replays a recording of frames, identically. The foundation of replay.
Usage examples
# listen to the bus
candump vcan0

# send a frame: identifier 0x123, 4 bytes
cansend vcan0 123#DEADBEEF

# generate random traffic every 200 ms
cangen vcan0 -I 200 -L 8 -D r

# spot the bytes that move
cansniffer vcan0

# record then replay
candump -l vcan0
canplayer -I candump-2026.log

ICSim: a dashboard to attack

ICSim simulates a dashboard: speedometer, turn signals, locks. It listens to a CAN bus and reacts to real frames. It is the classic training ground for practising decoding and injection, without a car.

Install and run ICSim
sudo apt-get install libsdl2-dev libsdl2-image-dev
git clone https://github.com/zombieCraig/ICSim
cd ICSim && make

# prepare the bundled virtual bus
./setup_vcan.sh

# the dashboard, then the remote control
./icsim vcan0
./controls vcan0

The controls window sends the legitimate frames, icsim displays them. It is up to you to find, with cansniffer, which frame commands the speed or the locks, then to forge it with cansend. This is exactly the approach of this site's Decoder and Reverse, but on a real piece of software.

SavvyCAN: graphical analysis

When the flow gets dense, the terminal shows its limits. SavvyCAN is a free graphical interface: capture, sorting, filters, signal graphs, replay, and importing DBC files to name the frames. It talks to SocketCAN as well as to serial hardware.

  • Connect to vcan0 or to a serial adapter (slcan) in a few clicks.
  • Capture then sort by identifier, highlighting the bytes that vary.
  • Signal analysis: you select bits, you watch the curve change.
  • Replay of captured frames, and manual sending, from the same window.

caring caribou: tooled-up CAN auditing

caring caribou goes higher than can-utils: it is an audit framework designed for security. It automates service discovery, targeted fuzzing and the exploration of UDS and XCP. You call it module by module.

Install caring caribou
git clone https://github.com/CaringCaribou/caringcaribou
cd caringcaribou
python3 -m pip install .
listener
Spots the active identifiers on the bus and their timing.
dump
Records the traffic for offline analysis.
fuzzer
Sends malformed frames to provoke abnormal reactions.
uds
Scans the diagnostic services, the data identifiers, the sub-functions.
xcp
Explores the XCP calibration protocol, often forgotten and talkative.
Examples
# list a module's help
caringcaribou uds -h

# listen to the bus and list the identifiers
caringcaribou listener

# discover an ECU's UDS services
caringcaribou uds discovery

Moving to a real bus: the hardware

The virtual world teaches the method; the hardware confronts you with the real thing. To connect a real CAN bus to a PC, a USB-CAN adapter is enough. Two families: those that expose an slcan serial interface, and those that show up directly as a SocketCAN interface.

Common adapters
HardwareInterfaceLevel
CANable (candlelight firmware)native SocketCAN (gs_usb)the simplest
CANable (slcan firmware)slcan serialsimple
CANtactslcan serialsimple
Arduino + MCP2515some tinkeringeducational
ESP32 + transceivercustom bridgeadvanced
Bring up an slcan adapter as interface can0
# the adapter shows up as /dev/ttyACM0, -s6 = 500 kbit/s
sudo slcand -o -c -s6 /dev/ttyACM0 can0
sudo ip link set up can0

# then all tools talk to can0 as they would to vcan0
candump can0

The framework