Vulnerabilities

Zero-Day Flaw Affects BMW’s ConnectedDrive Web Portal

The BMW ConnectedDrive Web portal was found to contain a vulnerability that could result in a compromise of registered or valid vehicle identification numbers, Vulnerability Lab warns.

<p class="MsoNormal"><span><span><strong>The BMW ConnectedDrive Web portal was found to contain a vulnerability that could result in a compromise of registered or valid vehicle identification numbers, Vulnerability Lab warns. </strong></span></span></p>

The BMW ConnectedDrive Web portal was found to contain a vulnerability that could result in a compromise of registered or valid vehicle identification numbers, Vulnerability Lab warns.

The security bug, affecting the BMW ConnectedDrive online service web-application, is a VIN (Vehicle Identification Number) session vulnerability, security researcher Benjamin Kunz Mejri reveals. VIN, also known as chassis number, is a unique code used in the automotive industry to identify individual vehicles.

The advisory published on Vulnerability Lab reveals that the issue is located in the session management of the VIN adding procedure and that a remote attacker could bypass the secure validation approval of the VIN. The validation doesn’t allow for non-existing numbers to be added to the configuration, but an attacker could tamper with a live session and bypass the invalid VIN exception to manipulate the configuration.

According to the researcher, the vulnerability is estimated to have High severity, with a CVSS (common vulnerability scoring system) base score of 6.0. Exploitation doesn’t require user interaction and can be performed via a low privileged web-application user account.

The security flaw was discovered in February this year, when the researcher also found a client-side cross site scripting vulnerability in the official BMW online service web-application. By exploiting this issue, an attacker could inject malicious script codes to the client-side of the affected module context, the researcher says.

This vulnerability is located in the `t` value (token) of the `passwordResetOk.html` web-application file and allows an attacker to inject own client-side script codes to the file. The attacker could leverage the GET request method for injection, the researcher explains in an advisory.

Advertisement. Scroll to continue reading.

“The vulnerability is located on the client-side of the affected BMW web-service. The attacker injects the payload after the secure token to execute the context in the passwordResetOk.html file. The vulnerability is a classic client-side cross site scripting web vulnerability,” the researcher also says.

Unlike the first security flaw, this security issue was assessed as Medium severity and has a CVSS score of 3.6. Exploitation doesn’t require a privileged user account but relies on low user interaction. According to the researcher, the successful exploitation of the issue results in session hijacking, non-persistent phishing, non-persistent external redirects to malicious source and non-persistent manipulation of affected or connected application modules.

As mentioned above, both flaws were found in February this year, when BMW was informed on the matter. The security researcher claims that he received feedback from BMW in early April, but doesn’t indicate that the issues were resolved. The researcher published Proof of Concepts (PoCs) for both flaws, in their respective advisories, along with recommendations on how they can be mitigated.

Related: BMW Patches Security Flaw That Let Hackers Open Doors

Related Content

Copyright © 2024 SecurityWeek ®, a Wired Business Media Publication. All Rights Reserved.

Exit mobile version