Tuesday, November 17, 2026

Mapping vehicle CAN buses with awesome-automotive-can-id, the community decoder ring index

Mapping vehicle CAN buses with awesome-automotive-can-id, the community decoder ring index

awesome-automotive-can-id aggregates crowdsourced CAN identifier and payload databases covering dozens of car brands, giving authorized automotive security researchers a single starting point for bus analysis.

TooliDoka/awesome-automotive-can-id — curated index of CAN ID and payload databases for many vehicle brands and models
CategoryAutomotive security reference / awesome-list
Primary UseLooking up documented CAN identifiers and payloads for a specific vehicle before deeper analysis with tools like canutils, SocketCAN, or ELM327-based sniffers in authorized labs
Safe UseIntended for cybersecurity researchers, reverse engineers, and automotive electronics enthusiasts working on vehicles they own or are explicitly authorized to test; also valuable for defenders designing in-vehicle intrusion detection baselines
Telemetry NoteThis is a passive reference list with no runtime footprint; the linked tools (CAN sniffers, OBD loggers) are observable only on the physical vehicle bus they are connected to

Not every security repository is a tool in the executable sense, and iDoka/awesome-automotive-can-id is a deliberate exception worth documenting. It is a curated index — an awesome list in the classic community tradition, released under CC0-1.0 — that collects references to CAN identifier and payload databases for an unusually broad range of vehicle manufacturers. With over a thousand stars and topics spanning automotive-security, car-hacking, obd2, socketcan, elm327, and vehicular-networks, it has become the de facto launchpad for anyone who needs to answer the question: what is already known about the CAN traffic of a particular make and model?

The README describes itself plainly as "an attempt to collect info about CAN IDs and payloads for various car brands/models in one place." That modest framing undersells the organizational effort involved. The index is broken down by manufacturer and often by model family, covering everything from BMW, Mercedes-Benz, and the full VAG group (Audi, Porsche, Volkswagen, Seat, Skoda) through Toyota, Tesla, Volvo, and Hyundai, and even extending to motorcycles from Ducati, KTM, Yamaha, and BMW. For anyone who has tried to reverse a vehicle bus from a cold start, that breadth alone is the value proposition.

Each entry links to an external resource rather than hosting the data itself, and the formats vary widely. Some links point to DBC files, the standard Vector-style database format that tools like SocketCAN-adjacent frameworks and SavvyCAN can load directly. The Lincoln MKZ entry from the abraham project, for example, is a .dbc file, as is the Infiniti G37 database. Others are Google Sheets spreadsheets, Markdown notes, .txt dumps, or .h header files containing CAN ID defines, such as the GMLAN_CAN_ID.h files for General Motors vehicles.

The Common section at the top deserves attention from professional readers because it aggregates the highest-leverage cross-vendor resources. The CommaAI opendbc project, described in the list as an effort to "democratize access to car decoder rings," is probably the single most complete open database of vehicle CAN definitions in existence. Alongside it are the OpenGarages raw link references, the RACELOGIC vehicle CAN database, and the rusEFI project's OEM documentation tree containing dump traces from a variety of vehicles. Anyone starting automotive research should read these five links before diving into the per-brand sections.

The granularity of some sections reflects genuine community reverse-engineering work. The Ford section is split by model — Fiesta, Mustang, Escape, Falcon, Transit — with entries noting bus speeds, model years, and platform variants, such as the Fiesta MK5 entry documenting an MS-CAN bus running at 125 kbps. The Kia section is anchored by the PolySync OSCC project, which documented the CAN interfaces for steering, throttle, and braking on the Kia Soul, with a note warning that all Kia models from 2014 onward except the Picanto share the same systems — exactly the kind of operational context that raw ID tables never convey.

From an authorized workflow perspective, this index sits at the very beginning of the automotive assessment pipeline. The typical pattern is: identify the target vehicle's make, model, and year; check this list for existing mappings; then validate against your own captures using canutils (candump, cansniffer), SocketCAN interfaces, slcan adapters, or ELM327-based hardware via the J1962 OBD-II connector. Pre-existing ID maps dramatically reduce the amount of blind differential sniffing needed, letting the researcher focus on behaviors rather than enumeration. The topics on the repository make clear this is exactly the audience intended: bus-monitoring, logger, sniffer, embedded.

It is worth being explicit about what this resource is not. It contains no exploits, no attack tooling, and no instructions for interfering with vehicle operation — it is documentation of how vehicles communicate internally, which is equally the raw material for defensive work. Security teams building CAN-based anomaly detection or fleet monitoring benefit from exactly the same ID and payload maps, because a baseline of expected arbitration IDs and message timing is a prerequisite for flagging injected or spoofed frames on a monitored bus. The line between offensive recon and defensive baselining here is entirely about intent and authorization.

The BMW section illustrates how deep some entries go beyond simple ID tables. It includes references to DBUS/IBUS/KBUS protocols, ECU-specific documentation for the Siemens MS42 and MS43 units in the E46 chassis, the E65 7 Series powertrain bus, an iDrive controller interface library for Arduino builds, and a reverse-engineered BMS/SBox hybrid battery module intended for EV conversion projects. That last entry is a reminder that a substantial fraction of the linked community is motivated by customization, retrofitting, and electric vehicle conversions rather than security research at all — the audiences overlap heavily on the underlying data.

Caveats a senior operator should keep in mind: link rot is the eternal enemy of curated lists, and several entries already point to web.archive.org snapshots of dead OpenGarages pages or to forum posts on non-English sites (a notable number of Land Rover, Lexus, and Jaguar entries live on Russian-language resources). Data quality is heterogeneous — a crowdsourced spreadsheet for a 2007 Freelander2 has not been through any validation process, and CAN maps frequently differ across model years, trim levels, and regional variants. Every identifier should be re-validated against your own captures before it is trusted for anything consequential.

Because the repository is CC0-1.0 licensed, the index itself carries no usage restrictions, though each linked resource retains its own license — relevant if you plan to fold a DBC file into a commercial product. The list is actively maintained on the main branch, with merged pull requests tracked via badges, so contributions of new vehicle data are the expected contribution model rather than code.

As a final placement note, awesome-automotive-can-id pairs naturally with tooling covered elsewhere on this blog: it supplies the semantic layer that turns a candump full of hex into named signals. If you work in authorized automotive assessment, vehicle forensics, or CAN intrusion detection research, bookmarking this repository and its Common section links is a five-minute investment that will save you weeks of redundant bus reverse engineering on well-documented platforms — and will tell you honestly, via an empty section, when you are on your own.

Official project repository for iDoka/awesome-automotive-can-id.
Download Tool

Educational analysis for authorized security professionals. Use only in controlled, authorized environments.

Sponsored
Share articleFacebookXLinkedIn

Continue exploring

Browse all articles →

0 comentários:

Post a Comment

Note: Only a member of this blog may post a comment.