← Threat Register

T-064 · Software, Hardware, and Architecture Transparency

Exploitation of insufficiently protected vehicle systems and components

Risk: Critical ReviewReview candidates available113 review candidates14 CVEs · 2 papersRegulatory

Threat analysis

Analysis / Description

Annex 5 subthreats include Cryptographic technologies can be compromised or are insufficiently applied, Parts or supplies could be compromised to permit vehicles to be attacked, Software or hardware development permits vulnerabilities, Network design introduces vulnerabilities, Unintended transfer of data can occur, Physical manipulation of systems can enable an attack

Assessment

Primary domain
Vehicle
Secondary domains
Infrastructure; User; Society
Affects
Vehicle, Infrastructure, User, Society
Impact
High (score 5)
Probability
Medium (score 4)
Source
UNECE R155, Annex 5, 4.3.7.

Impact rationale

"CATASTROPHIC" physical-safety impact is credible where a shared vulnerability permits unauthorized safety-critical control across many vehicles. Economic, societal and territorial impacts may be very serious when the weakness is widely deployed and difficult to patch.

Likelihood rationale

These are very likely threats. However, presence of a regulatory framework, and subsequent enforcement through type assessments. However, uniformity and depth of assessments vary from one technical service to another. Therefore, such threats could still exist and hence, is likely to occur.

Risk rationale

T-013, T-025, T-026, T-032, T-037, T-050 and T-051 already cover vulnerabilities, testing, requirements, AI exploitation and architecture. T-064 is the Annex 5 hardening umbrella linking those weaknesses to exploit scenarios.

External Evidence

Evidence supporting this threat

CVEs, academic research, strategic signals, real-world incidents and authoritative assessments from the correlation pipeline, plus public repositories from the existing evidence pipeline.

T-064
0
Accepted CVEs
0
Accepted Papers
0
Accepted Signals
0
Accepted Incidents
0
Accepted Assessments
0
Accepted Narratives
0
Repositories
113
Review Candidates
14 CVEs · 2 papers

Evidence strength describes the quality or authority of the source. Correlation status describes the automated relationship with this specific threat. Review status does not mean that the source itself is weak.

Evidence Requiring Review

Showing 30 of 113
Repository review
Correlation0.49

autocyberlab

Plausible match requiring review between github:roode2243/autocyberlab and T-064: structured overlap in assets: supply_chain, vehicle_ecu; protocols: uds; impacts: integrity; lifecycle: development_testing, governance; specific rules: external_interfaces, repository_rule_and_feature, repository_multi_axis_technical, repository_strong_structured_match; shared terms: subsequent, protected, exploitation, asset, uds, gateway, diagnostics, rather.

supply_chainvehicle_ecuudsintegritydevelopment_testinggovernancesubsequentprotectedexploitationasset
Technical correlation details
Evidence identifier
github:roode2243/autocyberlab
Evidence type
Repository
Evidence strength
Directly relevant technical repository
Confidence
low
Matched axes
assets, impacts, lifecycle, protocols
Rules fired
external_interfaces, repository_rule_and_feature, repository_multi_axis_technical, repository_strong_structured_match
Lexical0.03
Features0.51
Assets0.67
Protocols1.00
Attack vectors0.00
Impacts0.33
Rule contribution0.14
Context penalty0.00
Generic penalty0.00
Final score0.49
Repository review
Correlation0.48

UDS Security Access Code Location and Vulnerability Scanner

Plausible match requiring review between github:0xdq3/firmuds and T-064: structured overlap in assets: supply_chain, vehicle_ecu; protocols: uds; attack_vectors: ai_assisted; impacts: integrity; specific rules: repository_multi_axis_technical; shared terms: uds, manipulation, firmware, those, include, components, vulnerability, service.

supply_chainvehicle_ecuudsai_assistedintegritymanipulationfirmwarethoseincludecomponents
Technical correlation details
Evidence identifier
github:0xdq3/firmuds
Evidence type
Repository
Evidence strength
Strongly relevant technical repository
Confidence
low
Matched axes
assets, attack_vectors, impacts, protocols
Rules fired
repository_multi_axis_technical
Lexical0.03
Features0.57
Assets0.67
Protocols1.00
Attack vectors1.00
Impacts0.33
Rule contribution0.07
Context penalty0.00
Generic penalty0.00
Final score0.48
CVE review
Correlation0.48

CVE-2023-28905

Plausible match requiring review between CVE-2023-28905 and T-064: structured overlap in assets: infotainment; specific rules: infotainment_headunit; shared terms: infotainment, vulnerability.

infotainmentvulnerability
Technical correlation details
Evidence identifier
CVE-2023-28905
Evidence type
CVE
Evidence strength
Confirmed vulnerability record
Confidence
low
Matched axes
assets
Rules fired
infotainment_headunit
Lexical0.02
Features0.08
Assets0.33
Protocols0.00
Attack vectors0.00
Impacts0.00
Rule contribution0.04
Context penalty0.00
Generic penalty0.00
Final score0.48
CVE review
Correlation0.48

CVE-2023-28906

Plausible match requiring review between CVE-2023-28906 and T-064: structured overlap in assets: infotainment; specific rules: infotainment_headunit; shared terms: already, infotainment, vulnerability, service.

infotainmentalreadyvulnerabilityservice
Technical correlation details
Evidence identifier
CVE-2023-28906
Evidence type
CVE
Evidence strength
Confirmed vulnerability record
Confidence
low
Matched axes
assets
Rules fired
infotainment_headunit
Lexical0.04
Features0.08
Assets0.33
Protocols0.00
Attack vectors0.00
Impacts0.00
Rule contribution0.04
Context penalty0.00
Generic penalty0.00
Final score0.48
CVE review
Correlation0.48

CVE-2023-28909

Plausible match requiring review between CVE-2023-28909 and T-064: structured overlap in assets: infotainment; lifecycle: development_testing; specific rules: infotainment_headunit; shared terms: issue, infotainment, vulnerability, when.

infotainmentdevelopment_testingissuevulnerabilitywhen
Technical correlation details
Evidence identifier
CVE-2023-28909
Evidence type
CVE
Evidence strength
Confirmed vulnerability record
Confidence
low
Matched axes
assets, lifecycle
Rules fired
infotainment_headunit
Lexical0.03
Features0.14
Assets0.33
Protocols0.00
Attack vectors0.00
Impacts0.00
Rule contribution0.07
Context penalty0.00
Generic penalty0.00
Final score0.48
CVE review
Correlation0.48

CVE-2024-36842

Plausible match requiring review between CVE-2024-36842 and T-064: structured overlap in assets: infotainment; specific rules: infotainment_headunit; shared terms: issue, infotainment, hardware.

infotainmentissuehardware
Technical correlation details
Evidence identifier
CVE-2024-36842
Evidence type
CVE
Evidence strength
Confirmed vulnerability record
Confidence
low
Matched axes
assets
Rules fired
infotainment_headunit
Lexical0.04
Features0.08
Assets0.33
Protocols0.00
Attack vectors0.00
Impacts0.00
Rule contribution0.04
Context penalty0.00
Generic penalty0.00
Final score0.48
CVE review
Correlation0.48

CVE-2024-8356

Plausible match requiring review between CVE-2024-8356 and T-064: structured overlap in assets: infotainment; lifecycle: development_testing; specific rules: infotainment_headunit; shared terms: firmware, exploit, infotainment, vulnerability.

infotainmentdevelopment_testingfirmwareexploitvulnerability
Technical correlation details
Evidence identifier
CVE-2024-8356
Evidence type
CVE
Evidence strength
Confirmed vulnerability record
Confidence
low
Matched axes
assets, lifecycle
Rules fired
infotainment_headunit
Lexical0.03
Features0.12
Assets0.25
Protocols0.00
Attack vectors0.00
Impacts0.00
Rule contribution0.07
Context penalty0.00
Generic penalty0.00
Final score0.48
CVE review
Correlation0.48

CVE-2024-8357

Plausible match requiring review between CVE-2024-8357 and T-064: structured overlap in assets: infotainment; specific rules: infotainment_headunit; shared terms: exploit, issue, infotainment, vulnerability, hardware.

infotainmentexploitissuevulnerabilityhardware
Technical correlation details
Evidence identifier
CVE-2024-8357
Evidence type
CVE
Evidence strength
Confirmed vulnerability record
Confidence
low
Matched axes
assets
Rules fired
infotainment_headunit
Lexical0.04
Features0.08
Assets0.33
Protocols0.00
Attack vectors0.00
Impacts0.00
Rule contribution0.04
Context penalty0.00
Generic penalty0.00
Final score0.48
CVE review
Correlation0.48

CVE-2025-32058

Plausible match requiring review between CVE-2025-32058 and T-064: structured overlap in assets: infotainment, vehicle_ecu; specific rules: infotainment_headunit; shared terms: infotainment, vulnerability, ecu.

infotainmentvehicle_ecuvulnerabilityecu
Technical correlation details
Evidence identifier
CVE-2025-32058
Evidence type
CVE
Evidence strength
Confirmed vulnerability record
Confidence
low
Matched axes
assets
Rules fired
infotainment_headunit
Lexical0.03
Features0.16
Assets0.67
Protocols0.00
Attack vectors0.00
Impacts0.00
Rule contribution0.04
Context penalty0.00
Generic penalty0.00
Final score0.48
CVE review
Correlation0.48

CVE-2025-32059

Plausible match requiring review between CVE-2025-32059 and T-064: structured overlap in assets: infotainment, vehicle_ecu; lifecycle: development_testing; specific rules: infotainment_headunit; shared terms: issue, infotainment, vulnerability, when, ecu.

infotainmentvehicle_ecudevelopment_testingissuevulnerabilitywhenecu
Technical correlation details
Evidence identifier
CVE-2025-32059
Evidence type
CVE
Evidence strength
Confirmed vulnerability record
Confidence
low
Matched axes
assets, lifecycle
Rules fired
infotainment_headunit
Lexical0.04
Features0.22
Assets0.67
Protocols0.00
Attack vectors0.00
Impacts0.00
Rule contribution0.07
Context penalty0.00
Generic penalty0.00
Final score0.48
CVE review
Correlation0.48

CVE-2025-32061

Plausible match requiring review between CVE-2025-32061 and T-064: structured overlap in assets: infotainment, vehicle_ecu; lifecycle: development_testing; specific rules: infotainment_headunit; shared terms: issue, infotainment, vulnerability, when, ecu.

infotainmentvehicle_ecudevelopment_testingissuevulnerabilitywhenecu
Technical correlation details
Evidence identifier
CVE-2025-32061
Evidence type
CVE
Evidence strength
Confirmed vulnerability record
Confidence
low
Matched axes
assets, lifecycle
Rules fired
infotainment_headunit
Lexical0.04
Features0.22
Assets0.67
Protocols0.00
Attack vectors0.00
Impacts0.00
Rule contribution0.07
Context penalty0.00
Generic penalty0.00
Final score0.48
CVE review
Correlation0.48

CVE-2025-32062

Plausible match requiring review between CVE-2025-32062 and T-064: structured overlap in assets: infotainment, vehicle_ecu; lifecycle: development_testing; specific rules: infotainment_headunit; shared terms: issue, infotainment, vulnerability, when, ecu.

infotainmentvehicle_ecudevelopment_testingissuevulnerabilitywhenecu
Technical correlation details
Evidence identifier
CVE-2025-32062
Evidence type
CVE
Evidence strength
Confirmed vulnerability record
Confidence
low
Matched axes
assets, lifecycle
Rules fired
infotainment_headunit
Lexical0.04
Features0.22
Assets0.67
Protocols0.00
Attack vectors0.00
Impacts0.00
Rule contribution0.07
Context penalty0.00
Generic penalty0.00
Final score0.48
CVE review
Correlation0.48

CVE-2025-34251

Plausible match requiring review between CVE-2025-34251 and T-064: structured overlap in assets: infotainment; specific rules: external_interfaces; shared terms: permits, firmware, still, physical, control.

infotainmentpermitsfirmwarestillphysicalcontrol
Technical correlation details
Evidence identifier
CVE-2025-34251
Evidence type
CVE
Evidence strength
Confirmed vulnerability record
Confidence
low
Matched axes
assets
Rules fired
external_interfaces
Lexical0.04
Features0.08
Assets0.33
Protocols0.00
Attack vectors0.00
Impacts0.00
Rule contribution0.06
Context penalty0.00
Generic penalty0.00
Final score0.48
CVE review
Correlation0.48

CVE-2025-69515

Plausible match requiring review between CVE-2025-69515 and T-064: structured overlap in assets: infotainment; specific rules: infotainment_headunit; shared terms: issue, infotainment.

infotainmentissue
Technical correlation details
Evidence identifier
CVE-2025-69515
Evidence type
CVE
Evidence strength
Confirmed vulnerability record
Confidence
low
Matched axes
assets
Rules fired
infotainment_headunit
Lexical0.03
Features0.06
Assets0.25
Protocols0.00
Attack vectors0.00
Impacts0.00
Rule contribution0.04
Context penalty0.00
Generic penalty0.00
Final score0.48
CVE review
Correlation0.48

CVE-2026-49322

Plausible match requiring review between CVE-2026-49322 and T-064: structured overlap in assets: infotainment; specific rules: infotainment_headunit; shared terms: rather, cryptographic, infotainment, hardware, control, network.

infotainmentrathercryptographichardwarecontrolnetwork
Technical correlation details
Evidence identifier
CVE-2026-49322
Evidence type
CVE
Evidence strength
Confirmed vulnerability record
Confidence
low
Matched axes
assets
Rules fired
infotainment_headunit
Lexical0.04
Features0.06
Assets0.25
Protocols0.00
Attack vectors0.00
Impacts0.00
Rule contribution0.04
Context penalty0.00
Generic penalty0.00
Final score0.48
CVE review
Correlation0.48

CVE-2026-54413

Plausible match requiring review between CVE-2026-54413 and T-064: structured overlap in assets: vehicle_ecu; protocols: uds; specific rules: external_interfaces; shared terms: uds, diagnostics, ecu.

vehicle_ecuudsdiagnosticsecu
Technical correlation details
Evidence identifier
CVE-2026-54413
Evidence type
CVE
Evidence strength
Confirmed vulnerability record
Confidence
low
Matched axes
assets, protocols
Rules fired
external_interfaces
Lexical0.03
Features0.15
Assets0.33
Protocols0.33
Attack vectors0.00
Impacts0.00
Rule contribution0.09
Context penalty0.00
Generic penalty0.00
Final score0.48
Repository review
Correlation0.48

UDS Diagnostic Tool - ISO 14229-1

Plausible match requiring review between github:alvarodcastro/uds-shell and T-064: structured overlap in assets: supply_chain, vehicle_ecu; protocols: uds; lifecycle: development_testing, governance; specific rules: external_interfaces, repository_rule_and_feature, repository_multi_axis_technical, repository_strong_structured_match; shared terms: uds, diagnostics, safety-critical, type, testing, vulnerability, service, hardware.

supply_chainvehicle_ecuudsdevelopment_testinggovernancediagnosticssafety-criticaltypetestingvulnerability
Technical correlation details
Evidence identifier
github:alvarodcastro/uds-shell
Evidence type
Repository
Evidence strength
Strongly relevant technical repository
Confidence
low
Matched axes
assets, lifecycle, protocols
Rules fired
external_interfaces, repository_rule_and_feature, repository_multi_axis_technical, repository_strong_structured_match
Lexical0.03
Features0.38
Assets0.67
Protocols0.50
Attack vectors0.00
Impacts0.00
Rule contribution0.11
Context penalty0.00
Generic penalty0.00
Final score0.48
Repository review
Correlation0.48

Introduction

Plausible match requiring review between github:autosecurityy/automotive-cybersecurity-roadmap and T-064: structured overlap in assets: infotainment, vehicle_ecu; protocols: uds; impacts: integrity; lifecycle: development_testing, governance; specific rules: infotainment_headunit, repository_rule_and_feature, repository_multi_axis_technical, repository_strong_structured_match; shared terms: assessments., exploitation, asset, uds, firmware, exploit, gap, cryptographic.

infotainmentvehicle_ecuudsintegritydevelopment_testinggovernanceassessments.exploitationassetfirmware
Technical correlation details
Evidence identifier
github:autosecurityy/automotive-cybersecurity-roadmap
Evidence type
Repository
Evidence strength
Directly relevant technical repository
Confidence
low
Matched axes
assets, impacts, lifecycle, protocols
Rules fired
infotainment_headunit, repository_rule_and_feature, repository_multi_axis_technical, repository_strong_structured_match
Lexical0.03
Features0.28
Assets0.50
Protocols0.14
Attack vectors0.00
Impacts0.25
Rule contribution0.12
Context penalty0.00
Generic penalty0.00
Final score0.48
Repository review
Correlation0.48

🔒 NullSec Linux

Plausible match requiring review between github:bad-antics/nullsec-linux and T-064: structured overlap in assets: vehicle_ecu; protocols: uds; attack_vectors: ai_assisted; impacts: integrity; lifecycle: development_testing; specific rules: external_interfaces, repository_rule_and_feature, repository_multi_axis_technical, repository_strong_structured_match; shared terms: hardening, exploitation, uds, diagnostics, event, firmware, testing, requirements.

vehicle_ecuudsai_assistedintegritydevelopment_testinghardeningexploitationdiagnosticseventfirmware
Technical correlation details
Evidence identifier
github:bad-antics/nullsec-linux
Evidence type
Repository
Evidence strength
Strongly relevant technical repository
Confidence
low
Matched axes
assets, attack_vectors, impacts, lifecycle, protocols
Rules fired
external_interfaces, repository_rule_and_feature, repository_multi_axis_technical, repository_strong_structured_match
Lexical0.01
Features0.22
Assets0.25
Protocols0.20
Attack vectors0.20
Impacts0.25
Rule contribution0.16
Context penalty0.00
Generic penalty0.00
Final score0.48
Repository review
Correlation0.48

NullSec UDS

Plausible match requiring review between github:bad-antics/nullsec-uds and T-064: structured overlap in assets: vehicle_ecu; protocols: uds; lifecycle: development_testing, governance; specific rules: external_interfaces, repository_rule_and_feature, repository_multi_axis_technical, repository_strong_structured_match; shared terms: uds, diagnostics, firmware, testing, service, hardware, ecu, analysis.

vehicle_ecuudsdevelopment_testinggovernancediagnosticsfirmwaretestingservicehardwareecu
Technical correlation details
Evidence identifier
github:bad-antics/nullsec-uds
Evidence type
Repository
Evidence strength
Strongly relevant technical repository
Confidence
low
Matched axes
assets, lifecycle, protocols
Rules fired
external_interfaces, repository_rule_and_feature, repository_multi_axis_technical, repository_strong_structured_match
Lexical0.03
Features0.25
Assets0.33
Protocols0.25
Attack vectors0.00
Impacts0.00
Rule contribution0.11
Context penalty0.00
Generic penalty0.00
Final score0.48
Repository review
Correlation0.48

UDS / OBD-II ECU Simulation & Security Testing (ISO-TP over CAN)

Plausible match requiring review between github:basel-gomaa/uds-obd-security-labs and T-064: structured overlap in assets: vehicle_ecu; protocols: uds; impacts: integrity; lifecycle: development_testing; specific rules: external_interfaces, repository_rule_and_feature, repository_multi_axis_technical, repository_strong_structured_match; shared terms: hardening, protected, uds, diagnostics, manipulation, scenarios., type, components.

vehicle_ecuudsintegritydevelopment_testinghardeningprotecteddiagnosticsmanipulationscenarios.type
Technical correlation details
Evidence identifier
github:basel-gomaa/uds-obd-security-labs
Evidence type
Repository
Evidence strength
Strongly relevant technical repository
Confidence
low
Matched axes
assets, impacts, lifecycle, protocols
Rules fired
external_interfaces, repository_rule_and_feature, repository_multi_axis_technical, repository_strong_structured_match
Lexical0.03
Features0.45
Assets0.33
Protocols1.00
Attack vectors0.00
Impacts0.50
Rule contribution0.14
Context penalty0.00
Generic penalty0.00
Final score0.48
Repository review
Correlation0.48

🚗 TARA Pro — Automotive Cybersecurity Workbench

Plausible match requiring review between github:chanduthalathil-hash/tara-pro and T-064: structured overlap in assets: infotainment, supply_chain, vehicle_ecu; impacts: integrity; lifecycle: governance; specific rules: infotainment_headunit, external_interfaces, repository_rule_and_feature, repository_strong_structured_match; shared terms: cover, asset, gateway, transfer, gap, infotainment, user, impact.

infotainmentsupply_chainvehicle_ecuintegritygovernancecoverassetgatewaytransfergap
Technical correlation details
Evidence identifier
github:chanduthalathil-hash/tara-pro
Evidence type
Repository
Evidence strength
Strongly relevant technical repository
Confidence
low
Matched axes
assets, impacts, lifecycle
Rules fired
infotainment_headunit, external_interfaces, repository_rule_and_feature, repository_strong_structured_match
Lexical0.02
Features0.28
Assets0.60
Protocols0.00
Attack vectors0.00
Impacts0.33
Rule contribution0.15
Context penalty0.00
Generic penalty0.00
Final score0.48
Repository review
Correlation0.48

CARpwnd

Plausible match requiring review between github:crashoverid3/carpwnd and T-064: structured overlap in assets: infotainment, supply_chain; attack_vectors: ai_assisted; specific rules: infotainment_headunit, repository_rule_and_feature, repository_multi_axis_technical, repository_strong_structured_match; shared terms: exploitation, already, hence, exploit, very, infotainment, user, requirements.

infotainmentsupply_chainai_assistedexploitationalreadyhenceexploitveryuserrequirements
Technical correlation details
Evidence identifier
github:crashoverid3/carpwnd
Evidence type
Repository
Evidence strength
Directly relevant technical repository
Confidence
low
Matched axes
assets, attack_vectors
Rules fired
infotainment_headunit, repository_rule_and_feature, repository_multi_axis_technical, repository_strong_structured_match
Lexical0.02
Features0.17
Assets0.50
Protocols0.00
Attack vectors0.33
Impacts0.00
Rule contribution0.07
Context penalty0.00
Generic penalty0.00
Final score0.48
Repository review
Correlation0.48

Havne

Plausible match requiring review between github:erickramer42/havne and T-064: structured overlap in assets: supply_chain, vehicle_ecu; protocols: uds; lifecycle: development_testing; specific rules: external_interfaces, repository_rule_and_feature, repository_multi_axis_technical, repository_strong_structured_match; shared terms: parts, uds, diagnostics, shared, rather, sbom, still, vulnerability.

supply_chainvehicle_ecuudsdevelopment_testingpartsdiagnosticssharedrathersbomstill
Technical correlation details
Evidence identifier
github:erickramer42/havne
Evidence type
Repository
Evidence strength
Strongly relevant technical repository
Confidence
low
Matched axes
assets, lifecycle, protocols
Rules fired
external_interfaces, repository_rule_and_feature, repository_multi_axis_technical, repository_strong_structured_match
Lexical0.01
Features0.22
Assets0.40
Protocols0.33
Attack vectors0.00
Impacts0.00
Rule contribution0.11
Context penalty0.00
Generic penalty0.00
Final score0.48
Repository review
Correlation0.48

Automotive Cybersecurity TARA: 4-Corner Zonal Architecture (ISO/SAE 21434)

Plausible match requiring review between github:han6516/iso21434-tara-zonal-architecture-sdv and T-064: structured overlap in assets: infotainment, supply_chain, vehicle_ecu; protocols: uds; impacts: integrity; lifecycle: development_testing, governance; specific rules: infotainment_headunit, external_interfaces, repository_rule_and_feature, repository_multi_axis_technical, repository_strong_structured_match; shared terms: assessments, exploitation, asset, uds, gateway, firmware, cryptographic, introduces.

infotainmentsupply_chainvehicle_ecuudsintegritydevelopment_testinggovernanceassessmentsexploitationasset
Technical correlation details
Evidence identifier
github:han6516/iso21434-tara-zonal-architecture-sdv
Evidence type
Repository
Evidence strength
Strongly relevant technical repository
Confidence
low
Matched axes
assets, impacts, lifecycle, protocols
Rules fired
infotainment_headunit, external_interfaces, repository_rule_and_feature, repository_multi_axis_technical, repository_strong_structured_match
Lexical0.04
Features0.32
Assets0.43
Protocols0.20
Attack vectors0.00
Impacts0.25
Rule contribution0.17
Context penalty0.00
Generic penalty0.00
Final score0.48
Repository review
Correlation0.48

Automotive

Plausible match requiring review between github:i-can-hack/automotive and T-064: structured overlap in assets: vehicle_ecu; protocols: uds; lifecycle: development_testing; specific rules: external_interfaces, repository_rule_and_feature, repository_multi_axis_technical, repository_strong_structured_match; shared terms: uds, diagnostics, shared, transfer, include, enable, user, service.

vehicle_ecuudsdevelopment_testingdiagnosticssharedtransferincludeenableuserservice
Technical correlation details
Evidence identifier
github:i-can-hack/automotive
Evidence type
Repository
Evidence strength
Strongly relevant technical repository
Confidence
low
Matched axes
assets, lifecycle, protocols
Rules fired
external_interfaces, repository_rule_and_feature, repository_multi_axis_technical, repository_strong_structured_match
Lexical0.02
Features0.16
Assets0.20
Protocols0.25
Attack vectors0.00
Impacts0.00
Rule contribution0.11
Context penalty0.00
Generic penalty0.00
Final score0.48
Repository review
Correlation0.48

Doggie and evilDoggie Project Overview

Plausible match requiring review between github:infobyte/doggie and T-064: structured overlap in assets: vehicle_ecu; impacts: integrity; lifecycle: development_testing; specific rules: external_interfaces, repository_rule_and_feature, repository_strong_structured_match; shared terms: firmware, still, issue, testing, vulnerability, ecu, network.

vehicle_ecuintegritydevelopment_testingfirmwarestillissuetestingvulnerabilityecunetwork
Technical correlation details
Evidence identifier
github:infobyte/doggie
Evidence type
Repository
Evidence strength
Directly relevant technical repository
Confidence
low
Matched axes
assets, impacts, lifecycle
Rules fired
external_interfaces, repository_rule_and_feature, repository_strong_structured_match
Lexical0.02
Features0.25
Assets0.33
Protocols0.00
Attack vectors0.00
Impacts0.50
Rule contribution0.11
Context penalty0.00
Generic penalty0.00
Final score0.48
Repository review
Correlation0.48

🚗 AutoShield-CAN IDS

Plausible match requiring review between github:janani2436/can-bus-intrusion-detection-system and T-064: structured overlap in assets: vehicle_ecu; protocols: uds; attack_vectors: ai_assisted; lifecycle: development_testing, governance; specific rules: external_interfaces, repository_rule_and_feature, repository_multi_axis_technical, repository_strong_structured_match; shared terms: weakness, exploitation, asset, uds, shared, hardware, physical, architecture.

vehicle_ecuudsai_assisteddevelopment_testinggovernanceweaknessexploitationassetsharedhardware
Technical correlation details
Evidence identifier
github:janani2436/can-bus-intrusion-detection-system
Evidence type
Repository
Evidence strength
Directly relevant technical repository
Confidence
low
Matched axes
assets, attack_vectors, lifecycle, protocols
Rules fired
external_interfaces, repository_rule_and_feature, repository_multi_axis_technical, repository_strong_structured_match
Lexical0.02
Features0.29
Assets0.33
Protocols0.50
Attack vectors0.20
Impacts0.00
Rule contribution0.14
Context penalty0.00
Generic penalty0.00
Final score0.48
Repository review
Correlation0.48

EVCC-SIFT-Mutator ⚡🛡️

Plausible match requiring review between github:javastudentalex/evcc-sift-mutator and T-064: structured overlap in assets: supply_chain, vehicle_ecu; attack_vectors: ai_assisted; lifecycle: development_testing; specific rules: external_interfaces, repository_rule_and_feature, repository_multi_axis_technical, repository_strong_structured_match; shared terms: rather, gap, still, testing, vulnerability, where, hardware, when.

supply_chainvehicle_ecuai_assisteddevelopment_testingrathergapstilltestingvulnerabilitywhere
Technical correlation details
Evidence identifier
github:javastudentalex/evcc-sift-mutator
Evidence type
Repository
Evidence strength
Strongly relevant technical repository
Confidence
low
Matched axes
assets, attack_vectors, lifecycle
Rules fired
external_interfaces, repository_rule_and_feature, repository_multi_axis_technical, repository_strong_structured_match
Lexical0.01
Features0.18
Assets0.40
Protocols0.00
Attack vectors0.20
Impacts0.00
Rule contribution0.11
Context penalty0.00
Generic penalty0.00
Final score0.48
Research review
Correlation0.39

Enhancing AUTOSAR-Based Firmware Over-the-Air Updates in the Automotive Industry with a Practical Implementation on a Steering System

Plausible match requiring review between doi:10.48550/arxiv.2503.05839 and T-064: structured overlap in assets: vehicle_ecu; protocols: uds; impacts: integrity; lifecycle: development_testing; specific rules: external_interfaces; shared terms: uds, diagnostics, firmware, components, user, physical, architecture, design.

vehicle_ecuudsintegritydevelopment_testingdiagnosticsfirmwarecomponentsuserphysicalarchitecture
Technical correlation details
Evidence identifier
doi:10.48550/arxiv.2503.05839
Evidence type
Research
Evidence strength
Technical analysis
Confidence
low
Matched axes
assets, impacts, lifecycle, protocols
Rules fired
external_interfaces
Lexical0.04
Features0.37
Assets0.17
Protocols1.00
Attack vectors0.00
Impacts0.33
Rule contribution0.14
Context penalty0.00
Generic penalty0.00
Final score0.39
How evidence was matched to this threat

Technical surfaces: ECU, Gateway, Infotainment, UDS Diagnostics
Terms: -
CVE, paper, signal, incident, assessment and narrative correlations are generated by correlate_evidence.py. Repository mappings remain sourced from the existing evidence pipeline.

Regulatory traceability

UN Regulation No. 155

NCRC review-baseline mapping of T-064 to UN R155 requirements and Annex 5. Analytical traceability only, not a determination of compliance, non-compliance or legal effect.

RDW BASELINE

R155 coverage: 4.3.7 / Exploitable vulnerabilities and insufficient protection

Protected high-level baseline / direct.

R155 REQUIREMENT RELEVANCE

Main-text R155 CSMS, vehicle-type and type-approval relations. Expert review required.

No main-text R155 requirement relation was generated for this threat.
ANNEX 5 ANALYTICAL CANDIDATES

Analytical candidate relationships from the promoted review baseline.

5Mappings
5Review
reviewAnnex 5score 0.70
Part A / Table A1 / Ref 32.1

Physical manipulation or replacement of electronic hardware or sensor inputs

NCRC rationale: Threat register explicitly identifies Annex 5 area 4.3.7.

couldhardwaremanipulationphysicalprotectedvulnerabilities
Corresponding mitigations (1)
B / - / M9 Measures prevent and detect unauthorized access
reviewAnnex 5score 0.70
Part A / Table A1 / Ref 29.2

Circumvention of network separation to gain control

NCRC rationale: Threat register explicitly identifies Annex 5 area 4.3.7.

controlcouldnetworkprotectedvulnerabilities
Corresponding mitigations (1)
B / - / M23 Cybersecurity best practices are followed for software/hardware development, system design/integration, with appropriate testing
reviewAnnex 5score 0.55
Part A / Table A1 / Ref 18.1

External interfaces such as USB or other ports used as a point of attack

NCRC rationale: Candidate generated from shared technical concepts, an attack-path bridge, or multiple non-generic terms; expert review required.

suchthreats
Corresponding mitigations (1)
B / - / M22 Security controls are applied to external interfaces
reviewAnnex 5score 0.55
Part A / Table A1 / Ref 10.1

Virus embedded in communication media infects vehicle systems

NCRC rationale: Candidate generated from shared technical concepts, an attack-path bridge, or multiple non-generic terms; expert review required.

threats
Corresponding mitigations (1)
B / - / M14 Measures protect systems against embedded viruses/malware
reviewAnnex 5score 0.30
Part A / Table A1 / Ref 5.2

Communication channels permit manipulation of vehicle-held data/code

NCRC rationale: Candidate generated from shared technical concepts, an attack-path bridge, or multiple non-generic terms; expert review required.

manipulationpermitthreats
Corresponding mitigations (1)
B / - / M7 Access-control techniques and designs protect system data/code