start	end	text
0	2700	And OBD, what can we do with it?
190310	198150	So OBD-2 is a port that is usually located in the footwell of the driver's side of a car.
198150	201570	It's been mandated in cars since 1996.
201750	207690	OBD-2 standard itself defines both the electrical interface and messages.
207690	218430	Primarily the DTCs created to be used as a standard way for vehicles of any manufacturer to allow independent repair shops and dealers to test for emissions.
219070	221950	OBD-2 is a 16-pin connector port.
221950	232310	Although only 9 pins are mandated by the standard itself, most vehicles include an additional connectivity such as GM LAN or Chrysler CCD.
232670	245010	They are used at the dealership, for example, to update software on the ECUs, to perform additional software testing, or to troubleshoot problems specific to that vehicle's make and model.
247700	249140	Aftermarket OBD-2
249140	256140	At first, only standard OBD-2 connectors were able to read diagnostic information.
256140	263920	Manufacturers have been able to over the years reverse engineer the communication architectures to enhance their own offerings.
263920	281620	With the advent of inexpensive cellular, Wi-Fi, and Bluetooth components, aftermarket OBD-2 manufacturers have expanded their products to include entirely new classes of services, such as pay-by-the-mile insurance, vehicle use tracking, and commercial fleet management.
282060	284080	So what can we do with this?
284080	301580	Way more than transmitting DTC. CAN controls hundreds, if not thousands of sensors and ECUs that control everything from operating the vehicle, steering, accelerating, braking, all the way to infotainment and locking the doors.
301580	306100	All this information is being passed over the CAN bus.
306100	311200	The CAN bus is nothing more than a TCP-based packet switching network.
311200	318420	This is the same stuff that you see on your day-to-day jobs and most organizations' IT infrastructure.
318780	327560	The CAN protocol sends all this data to all the nodes on each giving bus, and each CAN frame includes a destination address.
327680	329540	How do we attack it?
329540	340920	OBD-2 aftermarket devices can potentially retrieve CAN traffic from outside of the vehicle from something like a Wi-Fi connectivity.
340920	347500	And pass it through unfiltered internal CAN bus through OBD-2 ports.
347500	357420	So nodes inside of the CAN network on the CAN bus are expected to ignore traffic that's not addressed to them.
357420	360400	But CAN frames don't have source addresses.
360400	366320	So there's no way for you to be able to tell legit data from spoof data.
366320	371480	This is where our journey begins as security researchers.
371480	379700	And for us to be able to go and continue to reverse engineer these protocols to understand exactly what's happening over these CAN buses.
379700	389500	For us to be able to use things such as OBD-2 potentially leveraging connectivity that's being built into the vehicles such as Wi-Fi or Bluetooth.
389500	397160	For us to be able to utilize those connectivities to leverage that to further attack.
398820	403100	Thank you. And if you have any questions, please don't hesitate to reach out.
403360	405240	My Twitter is Infinite.
405240	406620	And take care.