Scan CAN Bus for Diagnostic Modules - Metasploit
This page contains detailed information about how to use the post/hardware/automotive/identifymodules metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Module Overview
Name: Scan CAN Bus for Diagnostic Modules
Module: post/hardware/automotive/identifymodules
Source code: modules/post/hardware/automotive/identifymodules.rb
Disclosure date: -
Last modification time: 2020-09-22 02:56:51 +0000
Supported architecture(s): -
Supported platform(s): Hardware
Target service / protocol: -
Target network port(s): -
List of CVEs: -
Post Module to scan the CAN bus for any modules that can respond to UDS DSC queries
Module Ranking and Traits
Module Ranking:
- normal: The exploit is otherwise reliable, but depends on a specific version and can't (or doesn't) reliably autodetect. More information about ranking can be found here.
Basic Usage
There are two ways to execute this post module.
From the Meterpreter prompt
The first is by using the "run" command at the Meterpreter prompt. It allows you to run the post module against that specific session:
meterpreter > run post/hardware/automotive/identifymodules
From the msf prompt
The second is by using the "use" command at the msf prompt. You will have to figure out which session ID to set manually. To list all session IDs, you can use the "sessions" command.
msf > use post/hardware/automotive/identifymodules
msf post(identifymodules) > show options
... show and set options ...
msf post(identifymodules) > set SESSION session-id
msf post(identifymodules) > exploit
If you wish to run the post against all sessions from framework, here is how:
1 - Create the following resource script:
framework.sessions.each_pair do |sid, session|
run_single("use post/hardware/automotive/identifymodules")
run_single("set SESSION #{sid}")
run_single("run")
end
2 - At the msf prompt, execute the above resource script:
msf > resource path-to-resource-script
Required Options
- SESSION: The session to run this module on.
Knowledge Base
Scans the CANBUS for devices responding to UDS DSC queries. By trying to set the Diagnostic Session Control (DSC) devices that support UDS will typically respond with an error or an acknowldegment. We use this information to map out modules in a vehicle.
Options
STARTID
The CAN ID to start your scan from.
ENDID
The CAN ID to stop the CAN scan.
CANBUS
The bus to scan. See 'supported_buses' for a list of available buses
Scenarios
A Quick scan of buses from 0x600 to 0x7FF
hwbridge > run post/hardware/automotive/identifymodules CANBUS=can2 STARTID=0x600
Starting scan...
[*] Identified module 7e0
Scanned 504 IDs and found 1 modules that responded
7e0
Go back to menu.
Msfconsole Usage
Here is how the hardware/automotive/identifymodules post exploitation module looks in the msfconsole:
msf6 > use post/hardware/automotive/identifymodules
msf6 post(hardware/automotive/identifymodules) > show info
Name: Scan CAN Bus for Diagnostic Modules
Module: post/hardware/automotive/identifymodules
Platform: Hardware
Arch:
Rank: Normal
Provided by:
Craig Smith
Compatible session types:
Hwbridge
Basic options:
Name Current Setting Required Description
---- --------------- -------- -----------
CANBUS no CAN Bus to perform scan on, defaults to connected bus
ENDID 2039 yes End scan at this ID
SESSION yes The session to run this module on.
STARTID 1536 yes Start scan from this ID
Description:
Post Module to scan the CAN bus for any modules that can respond to
UDS DSC queries
Module Options
This is a complete list of options available in the hardware/automotive/identifymodules post exploitation module:
msf6 post(hardware/automotive/identifymodules) > show options
Module options (post/hardware/automotive/identifymodules):
Name Current Setting Required Description
---- --------------- -------- -----------
CANBUS no CAN Bus to perform scan on, defaults to connected bus
ENDID 2039 yes End scan at this ID
SESSION yes The session to run this module on.
STARTID 1536 yes Start scan from this ID
Advanced Options
Here is a complete list of advanced options supported by the hardware/automotive/identifymodules post exploitation module:
msf6 post(hardware/automotive/identifymodules) > show advanced
Module advanced options (post/hardware/automotive/identifymodules):
Name Current Setting Required Description
---- --------------- -------- -----------
VERBOSE false no Enable detailed status messages
WORKSPACE no Specify the workspace for this module
Post Actions
This is a list of all post exploitation actions which the hardware/automotive/identifymodules module can do:
msf6 post(hardware/automotive/identifymodules) > show actions
Post actions:
Name Description
---- -----------
Evasion Options
Here is the full list of possible evasion options supported by the hardware/automotive/identifymodules post exploitation module in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):
msf6 post(hardware/automotive/identifymodules) > show evasion
Module evasion options:
Name Current Setting Required Description
---- --------------- -------- -----------
Go back to menu.
Related Pull Requests
- #14202 Merged Pull Request: Implement the zeitwerk autoloader within lib/msf/core
- #8716 Merged Pull Request: Print_Status -> Print_Good (And OCD bits 'n bobs)
- #8338 Merged Pull Request: Fix msf/core and self.class msftidy warnings
- #7967 Merged Pull Request: DTC Improvements and Fixes
- #7795 Merged Pull Request: Hardware Bridge API. Initial bridge API that supports the HW rest pr…
Go back to menu.
See Also
Check also the following modules related to this module:
- post/hardware/automotive/can_flood
- post/hardware/automotive/canprobe
- post/hardware/automotive/diagnostic_state
- post/hardware/automotive/ecu_hard_reset
- post/hardware/automotive/getvinfo
- post/hardware/automotive/malibu_overheat
- post/hardware/automotive/mazda_ic_mover
- post/hardware/automotive/pdt
Authors
- Craig Smith
Version
This page has been produced using Metasploit Framework version 6.1.24-dev. For more modules, visit the Metasploit Module Library.
Go back to menu.