Research Article

A Comparative Study of JASO TP15002-Based Security Risk Assessment Methods for Connected Vehicle System Design

Table 8

CVSSv3 Basic Metrics [5] and Changes from CVSSv2.

Metric Name Short Description Changes from CVSSv2

AV Attack vector This metric reflects the context by which vulnerability exploitation is possible. Same metric

AC Attack ComplexityThis metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability Same metric, but rank reduced (3 2).

PR Privileges RequiredThis metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability. Expanded from Au (Authentication), and rank reduced (3 2).

UI User InteractionThis metric captures the requirements for a user, other than the attacker, to participate in a successful compromise of the vulnerable component. New metric. Whether a user (other than attacker)’s interaction is necessary for successful exploitation.

S Scoperefers to the collection of privileges defined by a computing authority (e.g., an application, an operating system, or a sandbox environment) when granting access to computing resources (e.g., files, central processing unit (CPU), memory, etc.). New metric. Whether the vulnerability spreads to other resources beyond the exploited component.

Im-C Confidentiality ImpactThis metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability. Same metric, only renamed from EF-C.

Im-I Integrity ImpactThis metric measures the impact to integrity of a successfully exploited vulnerability Same metric, only renamed from EF-I.

Im-A Availability ImpactThis metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerabilitySame metric, only renamed from EF-A.