BMW i/X/3/5/7 up to 2018 Head Unit HU_NBT protection mechanism

entryeditHistoryDiffjsonxmlCTI
CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.9$0-$5k0.00

A vulnerability has been found in BMW i, X, 3, 5 and 7 up to 2018 (Vehicle Software) and classified as critical. Affected by this vulnerability is an unknown function of the component Head Unit HU_NBT. The manipulation with an unknown input leads to a privilege escalation vulnerability. The CWE definition for the vulnerability is CWE-693. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

The Head Unit HU_NBT (aka Infotainment) component on BMW i Series, BMW X Series, BMW 3 Series, BMW 5 Series, and BMW 7 Series vehicles produced in 2012 through 2018 allows a local attack when a USB device is plugged in.

The bug was discovered 05/22/2018. The weakness was shared 05/31/2018 with Tencent (Website). The advisory is shared at securityfocus.com. This vulnerability is known as CVE-2018-9320 since 04/05/2018. An attack has to be approached locally. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 02/10/2020). Due to its background and reception, this vulnerability has a historic impact.

The vulnerability was handled as a non-public zero-day exploit for at least 9 days. During that time the estimated underground price was around $0-$5k.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 104258). The entries 118484, 118485, 118486 and 118488 are related to this item.

Productinfoedit

Type

Vendor

Name

CPE 2.3infoedit

CPE 2.2infoedit

CVSSv3infoedit

VulDB Meta Base Score: 5.9
VulDB Meta Temp Score: 5.9

VulDB Base Score: 4.1
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.8
NVD Vector: 🔍

CVSSv2infoedit

AVACAuCIA
🔍🔍🔍🔍🔍🔍
🔍🔍🔍🔍🔍🔍
🔍🔍🔍🔍🔍🔍
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfoedit

Class: Privilege escalation
CWE: CWE-693
ATT&CK: Unknown

Local: Yes
Remote: No

Availability: 🔍
Status: Not defined

Price Prediction: 🔍
Current Price Estimation: 🔍

0-Dayunlockunlockunlockunlock
Todayunlockunlockunlockunlock

Threat Intelligenceinfoedit

Threat: 🔍
Adversaries: 🔍
Geopolitics: 🔍
Economy: 🔍
Predictions: 🔍
Remediation: 🔍

Countermeasuresinfoedit

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfoedit

04/05/2018 🔍
05/22/2018 +47 days 🔍
05/22/2018 +0 days 🔍
05/31/2018 +8 days 🔍
05/31/2018 +0 days 🔍
06/01/2018 +1 days 🔍
02/10/2020 +619 days 🔍

Sourcesinfoedit

Advisory: securityfocus.com
Organization: Tencent
Status: Not defined

CVE: CVE-2018-9320 (🔍)
SecurityFocus: 104258 - Multiple BMW Products Multiple Security Vulnerabilities

See also: 🔍

Entryinfoedit

Created: 06/01/2018 09:23 AM
Updated: 02/10/2020 06:02 PM
Changes: (4) vulnerability_discoverydate advisory_company_name source_securityfocus_date source_securityfocus_class
Complete: 🔍

Comments

No comments yet. Please log in to comment.

Want to stay up to date on a daily basis?

Enable the mail alert feature now!