{"id":134,"date":"2008-02-10T22:07:06","date_gmt":"2008-02-11T06:07:06","guid":{"rendered":"http:\/\/cubist.cs.washington.edu\/Security\/2008\/02\/10\/security-review-gm-onstar\/"},"modified":"2008-02-18T22:23:59","modified_gmt":"2008-02-19T06:23:59","slug":"security-review-gm-onstar","status":"publish","type":"post","link":"https:\/\/secblog.cs.washington.edu\/Security\/2008\/02\/10\/security-review-gm-onstar\/","title":{"rendered":"Security Review: GM Onstar"},"content":{"rendered":"<p>GM&#8217;s OnStar service has been a sucess for several years now. It gives many services to people with GM vehicles. It provides some very powerful features such as GPS tracking, stolen vehicle slowdown, remote unlock and emergency services. However the technology imposes potential for exploitation.<\/p>\n<p><!--more--><\/p>\n<p><strong>Assets &amp; Security Goals<\/strong><\/p>\n<p>The vehicle itself is a valuable property asset, as vehicles can be sold as parts (which can be worth more than the car) or for illegal export.<\/p>\n<p>The vehicle&#8217;s tracking information also is valuable information in learning about the vehicle&#8217;s owner.<\/p>\n<p><strong>Threats\/Adversaries<\/strong><\/p>\n<p>Other automakers may want to tarnish GM&#8217;s reputation.<\/p>\n<p>Enemies of the vehicle&#8217;s owner  may use it OnStar to their advantage.<\/p>\n<p>Car theives can use OnStar to potentially find vehicles.<\/p>\n<p><strong>Weaknesses<\/strong><\/p>\n<p>Since OnStar is both a computerized and call-center based service, social engineering techniques can be used to make the vehicle vulnerable to exploitation.<\/p>\n<p>If someone knew the OnStar specification, the attacker could control some vital parts of the system (locking, fuel system, lights).<\/p>\n<p><strong>Defenses<\/strong><\/p>\n<p>&#8220;Secure cellular connection that is authorized and authenticated  by an OnStar server &#8221; By authenticating communications, the vehicle should be more secure. Forgery of messages should be prevented by authorization given the system implements the proper authentication controls.<\/p>\n<p>Security by obscurity &#8211; the OnStar technology is proprietary and is as well as well known as Windows CE or other platforms with vulnerabilities that are used in similar technologies (BMW, Fiat, Mitsubishi)<\/p>\n<p><a href=\"http:\/\/www.pctoday.com\/editorial\/article.asp?article=articles%2F2005%2Ft0310%2F05t10%2F05t10.asp\">http:\/\/www.pctoday.com\/editorial\/article.asp?article=articles%2F2005%2Ft0310%2F05t10%2F05t10.asp<\/a><\/p>\n<p>Since the OnStar system is not based on a well documented system,  it is harder to find vulnerabilities other than reverse engineering, inspecting at the assembly level, or insider information.<br \/>\n<strong>Conclusions<\/strong><\/p>\n<p>There are valuable assests tied in with OnStar. However, due to the obscurity of the system, it should be relatively secure until the vulnerabilities are found. Social engineering could bypass these methods due to the call center approach, and could pose to be the biggest problem with securing the vehicle and its contents as an asset.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>GM&#8217;s OnStar service has been a sucess for several years now. It gives many services to people with GM vehicles. It provides some very powerful features such as GPS tracking, stolen vehicle slowdown, remote unlock and emergency services. However the &hellip; <a href=\"https:\/\/secblog.cs.washington.edu\/Security\/2008\/02\/10\/security-review-gm-onstar\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":34,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[32],"class_list":["post-134","post","type-post","status-publish","format-standard","hentry","category-security-reviews","tag-security-review"],"_links":{"self":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/posts\/134","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/users\/34"}],"replies":[{"embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/comments?post=134"}],"version-history":[{"count":0,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/posts\/134\/revisions"}],"wp:attachment":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/media?parent=134"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/categories?post=134"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/tags?post=134"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}