iThome CyberSec2020-Chaos Of Vehicle Communications

Transcript

1. NotSurprised @ iThome notsurprisedtw@gmail.com
2. https://speakerdeck.com/notsurprised/ithome-cybersec2020-chaos-of-vehicle-communications
3. > • Background – Introduction – Protocols – ECU/Components • OMA DM – Parser problems – Self-defined – Inconsistency • Summary – Recap – Suggestion – Resource
4. > NotSurprised Intro • UCCU Hacker • AIS3 2016 trainee • HITCON Defend 2018 3rd (etc.) • SITCON 2019 speaker • MOPCON 2019 speaker • Becks.io#5 speaker • ITRI Engineer (serve my country) • 5-years Bachelor & Master of NSYSU Email : notsurprisedtw@gmail.com Skill • Windows Kernel Driver (Minifilter) • Penetration Test (Web) • Malware Analysis (Ransomware) • Ethereum Smart Contract (Solidity) • Car Security (OMA DM)
5. • • •
6. > Drone, IoT, AI Manufacture, AI Car(VANET) sounds great, but… Are They Secure?
7. >
8. > • Charlie Miller Jeep Cherokee – Charlie Miller share series attack vectors • Tencent KeenLab Tesla Model S • ADCD Key Signal repeat – Proof that signals can be simply trigger and enhance to repeat received signals • PWN2OWN 2019 Tesla Model 3 • Car2go Auto Review Application in Chicago – This connect to server problem, review mechanism can be fraud and unlock the car with fake person id
9. > • RFID • CAN Bus • Bluetooth • Cellular Network (Internet) • VANET • OMA DM
10. > Car Internal Communication Car external communication Key Manufacture server
11. >
13. >
14. > • RFID(Radio Frequency Identification), radio also • In vehicle, long distance, usually in high frequencies, UHF root@kali:~# nfc-list nfc-list uses libnfc 1.7.1 NFC device: pn532_uart:/dev/ttyUSB0 opened 1 ISO14443A passive target(s) found: ISO/IEC 14443A (106 kbps) target: ATQA (SENS_RES): 00 04 UID (NFCID1): 3c 3d f1 0d SAK (SEL_RES): 08 root@kali:~# nfc-mfsetuid 3c3df10d NFC reader: pn532_uart:/dev/ttyUSB0 opened Sent bits: 26 (7 bits) Received bits: 04 00 Sent bits: 93 20 Received bits: 0c 5c ee 0d b3 Sent bits: 93 70 0c 5c ee 0d b3 5c c2 Generate fake RFID key RFID Reader with Arduino
15. > • Signal Amplification Relay Attack • Original designed to copy for backup and become all in one RFID key in personal used • Can copy 125 kHz (“low frequency”) RFID • Can not copy 13.56MHz (“high frequency”) NFC
16. >
17. >
18. >
19. > • Best way to get into CAN bus – Compromise the car’s mini computer ( OS: QNX, Win CE, Linux, Android, Green Hills) – As a component in car, mini computer connect to CAN bus and dash board • Message on CAN bus system – CAN message format • ISO 11519-2 / ISO 11898:1993 / ISO 11898:1995 • Make largest privilege code in your broadcast packet – Diagnostic trouble code format • Sometime trigger automatic reaction • Aircraft also use CAN bus – Same problem that microcontroller is the last defend line in simple aircraft
20. >
21. > • CAN – ISO-TP (ISO 15765-4) – CANopen – GMLAN bus • SEA J1850 – PWN – VPW • KWP – KWP2000 (ISO 9141-2) – ISO 14230-4 • LIN Bus • MOST – Independent from bus line, for IVI, connect to speaker and cellular network. • FlexRay • Ethernet
22. > credit :
23. > credit :
24. > credit :
25. > • FlexRay bus – Fastest – Expensive – Top class car – Sensitive • CAN bus – Good CP value – Widely used credit :
26. > • OBDII (On-Board Diagnostic System II) ft. EcomCat credit :
27. > ECOM2 OBDII Cable US $203.37 ValueCan3 OBDII Cable US $395.00
28. > ELM327 OBDII Cable US $8.40~$2.50
29. > Expensive OBD2 Cable Cheap OBD2 Cable Normal Limited Usually not Sometimes GUI / Auto Link Open Source / Self-defined High Low (china copycat) Yes No Lots None Yes None
30. > Some interesting tool: • ICSim: Instrument Cluster Simulator – For Can
31. > • MyCar, CarDoctor, Car Scanner – Type of product connect to OBDII and APP – Control your car’s status to prevent frauded by repair shop – Usually Bluetooth(shorter distance, more secure), WIFI/3G/4G – As IoT, default AC/PW remain problem – Bluetooth default paring key: 0000/1234 (sometime even not give a request)
32. > • Using uuid and handle (company identifier) primary and characteristic command. • Sometime you can brutal force it or OSINT for hint. • MiBand2 no auth key, MiBand3 has breakable auth key.
33. > • Torque • Car scanner • OBD Auto Doctor
34. > • ELM327 OBD2 BLE • Cannot change PIN • Support several client APP credit :
35. > • ELM327 OBD2 WiFi • Default IP & Port • Support several client APP
36. >
38. > credit : Semantic
39. > • HTTP sniffer than you will get the AC/PW • Door seq. being shown on URL query as plaintext • Even you have no AC/PW, you can unlock most door remote by SQLi • There's a password to switch to setting mode on product’s user manual, you can find it on internet. e.g. #123456#
40. > • A human-readable JSON protocol “encrypted” with an easily reversible autokey (-85) XOR cipher and a binary DES-encrypted configuration (AC/PW : admin/admin)
41. > • Not just Bluetooth, also using GPS and a cellular connection to extend their range to anywhere with an internet connection. credit :
42. > • Acoount & Password is default in factoryBootstrap and popular • User Guide which contain AC/PW public on internet – https://fccid.io/2AEB4AG21/User-Manual/User-manual-3104674 credit :
43. > • Such Vulhub website provide by MyCar Vendors credit :
44. > • SQLi to other account and launch other’s car engine by web API credit :
45. credit : BUG BUG CVE CVE MyCar Vendor MyCar Vendor MyCar Vendor MyCar Vendor
48. > credit : Automotive Electronics
49. > credit :
50. > credit : LGACL Simulator
51. Vehicular Ad Hoc Network On-Board Unit, OBU Road Side Unit, RSU • On board device to receive/send message system • Combined with sensors • microcontroller, speed sensor, brake sensor, radar, GPS, etc… • Road side sensor to receive/send message system • Has computing abilities • Co-work with OBU to make V2V communication happened • RSU can connect to central control center to make road state under control > credit : yenchih.kuo@NSYSU
52. • Communication between car：Vehicle to Vehicle, V2V • Communication between car and road：Vehicle to infrastructure, V2I • Dedicated Short Range Communications (DSRC) • 5.85GHz~5.925GHz • Infrared、RFID、IEEE802.11p、IEEE1609 • in IEEE1609.x Wireless Access in the Vehicular Environment (WAVE) • Transmission Rate：3~27Mbps • Most Range：1km > credit : yenchih.kuo@NSYSU
53. > • Every sec, car will delivered its own basic info. Including highway ID, delivered time, position, speed. • Attacker can overwrite Beacon info to make MDS make mistake. • Therefore, vehicle need to confirm pkg from valid node, and check checksum. VANET Attack can conclude into 5 phases: • Abnormal Data Check • Alert Check • Node Oriental Detecting Method • Data Oriental Detecting Method • Privacy
54. > In next section →
55. > In next section →
56. > • JTAG – A kind of debugging protocol, can download and upload the firmware, find the PIN on manual • JTAGulator – A tool to help researcher find the JTAG PIN on chip credit : attify
57. > • SWD (serial wire debug) – A kind of debugging protocol, support by STM32F4 series (STM32F4 is the most widely used car chip) • STM32F4 Discovery Kit – A debug tool provide by ST themself credit : st
58. > • IVI (In-Vehicle Information System) • MCU (Microcontroller Unit) credit : iotm2mcouncil
59. > MobilePhone / Server HMI MicroController HTTP Modbus Canbus Device PLC ECU No No / TLS1.2 No Strong Normal Weak Lots Few Few *Public Private *Public *Few *Few Lots Remote / Extranet Remote / Extranet Physical / Short-dist / Remote
60. > • Most are targeted attack • Vehicle security base on close-source and inconsistency, just like OT • Revenue is totally different class in IoT device, worth targeted attack • As AI raise, automatous vehicle definitely need standards to connect to the road system and collect info for AI, therefore, it bring problems in security
61. >
62. >
63. >
64. >
65. >
66. • • •
67. Intro • End-End Web Service Developer • NTUST Information & Data Sciense Master • HITCON 2019 speaker • ITRI Engineer (serve country) Dylandy
68. > • OEM (Original Equipment Manufacturer) / ODM (Original Design Manufactures) try to add remote updating ability to the vehicle ECU • There need a Update Solution standard to support several ECU vendors' remote updating requirements
69. > • Open Mobile Alliance (OMA) designed a protocol for Device Management (DM), to remote implement UPDATE, MANAGE, CONTROL and BACKUP. Car Vendors can use this protocol to remote control version update and retrieve data. • Automotive Grade Linux (AGL) is sub-org under The Linux Foundation which engage in cross industry requirements for internet of car. Recently, AGL try to defined OMA DM 2.0 to become car communication standard. • Tesla convince that their protocol is too rough and their last line in security protection is Black Box, open source will make their products in risk.
70. > • OMA DM is a device management protocol for server to control the client device. • OMA DM include following major phases: – Generic device information maintain (DevInfoMO, DmAccMO, DCMO) – Firmware maintain (FUMO) – Software maintain (SCOMO) • OMA DM now has two version release: – OMA DM I (complete) • base on SyncML (Synchronization Markup Language) data format, OMA also give a project as syncml rtk which plays as communication protocol of SyncML – OMA DM II (uncomplete) • base on JSON data format, it simply use HTTP as communicate protocol • only main protocol update to version II, not FUMO, SCOMO, or any else
71. > • OMA DM 1.3 Communication Flow SyncML
72. > • OMA DM 2.0 Communication Flow JSON
73. > • How to Registration? How to identify response with Async Report?
74. > • First Time Package1 session establish: • Else: Factory Bootstrap Device Serial Number Match Server’s Unregister Device Auth > > > Some else RFC2617 Headers (e.g. Authorization)
75. > • That means registration key is store on microcontroller DB as un-encrypted state and can be inferred • You can register a fake client just like which we infer door number that mentioned in Section 1 IoT part
76. > • TLS/SSL is recommended in OMADM 2.0 • RFC2617 Basic Authentication Schema MUST be supported (newest: RFC 7617 (2015)) • RFC 2617 security options are optional. If Server doesn’t set QOP, Client will work as RFC 2069. • Basic Authentication Schema is easy attack by MITM. Attacker can easily set OFF on QOP to let Client use RFC 2069. • Moreover, there’s no mechanism to let Client check Server identification. • RFC 2617 block user to use STRONG hash algorithm to store sensitive data like PSW, they defined as recoverable value. HTTP PlainText HTTP Basic and Digest Access Authentication HTTPS/SSL HTTPS/TLS < <
77. We all know where recommends are going ¯\_(ツ)_/¯
78. > • HTTP Public
79. > • OMA DM Modules and Functions – Command Dealer – Parser & Database maintainer – Package Handeler • OMA DM Data structures
80. > • Table Name?
81. > • Table Name?
82. > • Database type storage in OMA DM – Pros • Insert / Update / Parse can easily use database schema mechanism to check DDF invalid – Cons • Need more designing on table name also reach the consensus between Server & Client • XML type storage in OMA DM – Pros • easily fit the document designing – Cons • Insert a new MO tree will be hard to check if is valid DDF
83. > • Actually Usage of Value?
84. > • Cross Protocol Version: – DataBuffer stream boundary different in SML & HTTP (1st command result following with 1st data /1st command result code with 2nd command result code) – Command method not backward compatible (Ver2 not support REPLACE command) • OMA DM NodeName & SQL Syntax conflict: – urn:oma:mo:fumo:1.0/<x>/update • A lot of Extension in OMA DM tree: (there can not be multiple tables in same name) – urn:oma:mo:oma-dm-devinfo:1.2/<x>/Ext – urn:oma:mo:oma-dm-dmacc:1.2/<x>/Push/GCM/Ext – urn:oma:mo:fumo:1.0/<x>/Ext • Result Code inconsistency: – Sometime diff MO module use same result code, sometime not. • Same MO module, different DDF
85. > • Request Launching in different way – Server use method commands – Client use Generic Alerts (the one they usually used is to respond the results of async commands like EXEC) • Alert Type – urn:oma:at:dm:2.0:BootstrapComplete – urn:oma:at:dm:2.0:ClientInitiatedMgmt – urn:oma:at:dm:2.0:ServerInitiatedMgmt – urn:oma:at:scomo:1.1:UpdateUserRequest – org.openmobilealliance.dm.firmwareupdate:update – org.openmobilealliance.dm.firmwareupdate:downloadandupdate
86. > • urn:oma:mo:moid:1.0// – Cannot resolve, there’s two MO instances. • urn:oma:mo:moid:1.0/left/Data/1/Value – identifies one nodes; the moroot1/Data/1/Value • Ellipsis: Usually use on MIID, this regards as only one node/value come up as result. • Real Name: The actually node name.
87. > • urn:oma:mo:moid:1.0/(x)/Data/*/Value?nv=(x)/ID:GPS – identifies two nodes, error – the moroot1/Data/1/Value and moroot1/Data/2/Value node • x-name: the DM Client MUST resolve only one node that satisfies all corresponding nv fields for this x-name component; if multiple nodes are resolved, an error code MUST be returned • Wildcard: the DM Client MUST address all nodes at the specified location
88. > • In fact, Client and Server should share same MO trees (even though Server will manage lots of Clients, but server should sync every Client) • This over-freedom parser should only implement on Server backend control panel, or better not exist • Server and Client should send what they exactly needed rather than making parser more complicated • It is strongly suggest that not to allow # ; = > < this kind of SQL symbol as valid characters in every node in URI
89. > • Too complicate for Developer to implement property – With dynamic-changing table schema in SCOMO – Apply to self-defined table schema with different Vendors’ clients • SQLinjection with PlainText HTTP body (especially URI) • Sometime Vendors’ clients simply send sub-tree in it’s own style. (e.g. strings in integers, arrays in different JSON objects)
90. > & • There’s no token designed(relative key in OMADM1.0, but not in OMADM2.0) and authenticate mechanism(registration) in this protocol. • MITM still problem here. (RFC2617 doesn’t work to prevent this link attack.) • There’s no checksum confirmed mechanism for FUMO,(firmware update module) client cannot even check if it is runnable or not before it exec the binary. • There’s checksum confirmed mechanism for SCOMO (software update module), however, download source URL still can be a trap. (Server not even going to auth or check Remote Repository Server status and give a valid token let client to confirm source)
91. > & Server Client Hacker Un-encrypted DB Fake Request Hacking Payload Response e.g. DevID (API key)
92. > & Benign Server Benign Client Hacker Request Update Fake Command Fake Request Response
93. > Hacker Request Update Malicious Server Benign Server Benign Client Compromised Switch Hack Request Update Malicious Payload DownloadURL Malicious Payload DownloadURL
94. > Hacker Compromised Remote Repository Benign Server Benign Client Hack Auth Sync???? Update Request TargetURL Response Download Request Malware / File Name Command injection e.g. Ruby,Net::FTP command injection e.g. Unsnenitize file name donwload
95. > Hacker Request Update Compromised Server Client Fake Command Server Control Panel Hack ECU 1. Return shell with malicious update 2. finding ECU ID from Brutal Force OMA DM component db information with GET cmd 3. Sending Canbus modified malicious component application e.g. Node.js ft. misconfigure debugger handshake Allow command injection
96. • • •
97. > RDS Bluetooth WiFi SD USB GPS Infotainment 3G/4G OBD2 Physical Remote Android Apps Remote Repository MyCar server Update server
98. > • In IoT, OT, and Vehicle communication, plaintext and default AC/PW still make serious problems • Latest Cross-Industry features (AI manufacture, AI medication, AI car) still not take Information Security as a serious problem, then come out with lots of vulnerabilities application • In past, low revenues device (PC, IoT) can be find out exploit value by black industry. Apparently, vehicle with its high value deserve to own its targeting attack, and it’s worthy • Vehicle security can be a research draft of aircraft, it’s really sensitive to country security • OMA DM 2.0 is a protocol that need to harden. Should take serious concern on security issues on its document
99. > • Supply chain attack make vendors pay attention on every third-party libraries (& Remote Repository Server) • Make sure to use BL/WL mechanism and Hash check • Cipher and CA always enhance your communication, use them • Physical attack cannot avoid, but take care every addon on your car and make sure to change your AC/PW • Every remote access to CAN bus components (OBDII, MyCar, ECU update) should apply auth confirm & encrypted communication. Vendors’ Web should apply vulnerabilities scanning to fix bugs, avoid brutal force and information leak. • Mini computer is the major component in all attack vectors, Application Whitelist can ease the lost after compromised by hacking
100. > • http://www.openmobilealliance.org/ • http://illmatics.com/Remote%20Car%20Hacking.pdf • https://ioactive.com/pdfs/IOActive_Adventures_in_Automotive_Networks_and_Control_Units.pdf • https://www.sans.org/reading-room/whitepapers/threats/hacking-bus-basic-manipulation-modern- automobile-through-bus-reverse-engineering-37825 • http://www.aut.upt.ro/~pal-stefan.murvay/papers/dos-attacks-controller-area-networks-fault- injections-from-software-layer.pdf • https://media.defcon.org/DEF%20CON%2027/DEF%20CON%2027%20presentations/DEFCON-27-Jmaxxz- Your-Car-is-My-Car-Code-6e0e599/ • https://www.shs.edu.tw/works/essay/2012/11/2012111421572430.pdf • https://hackaday.com/2019/06/10/takatas-deadly-airbags-an-engineering-omnishambles • https://blog.avast.com/hacker-breaches-gps-service-of-27000-cars • https://www.zdnet.com/article/dhs-warns-about-can-bus-vulnerabilities-in-small-aircraft • https://www.outilsobdfacile.com/vehicle-list-compatible-obd2 • https://github.com/gmacario/easy-build • https://www.st.com/resource/en/user_manual/dm00039084-discovery-kit-with-stm32f407vg-mcu- stmicroelectronics.pdf • https://www.elmelectronics.com/wp-content/uploads/2017/01/ELM327DS.pdf
101. >
102. >