{"id":207,"date":"2008-03-16T16:22:25","date_gmt":"2008-03-17T00:22:25","guid":{"rendered":"http:\/\/cubist.cs.washington.edu\/Security\/2008\/03\/16\/virus-laden-hardware-emerges\/"},"modified":"2008-03-16T16:22:25","modified_gmt":"2008-03-17T00:22:25","slug":"virus-laden-hardware-emerges","status":"publish","type":"post","link":"https:\/\/secblog.cs.washington.edu\/Security\/2008\/03\/16\/virus-laden-hardware-emerges\/","title":{"rendered":"Virus laden hardware emerges"},"content":{"rendered":"<p>While the idea of software viruses\u00a0is by no means new to those who work with computers, a new vector of attack seems to be developing in the form of hardware shipped from the manufacturer that is already infected with malware. In the past few weeks, a set of digital peripherals, particularly USB picture frames and IPods, have been found to contain one or more malicious executables. With such a method of delivery, it seems that the security industry may need to rethink what can and cannot be considered secure.<\/p>\n<p>\u00a0<a href=\"http:\/\/www.cnn.com\/2008\/TECH\/ptech\/03\/13\/factory.installed.virus.ap\/index.html?iref=mpstoryview\">http:\/\/www.cnn.com\/2008\/TECH\/ptech\/03\/13\/factory.installed.virus.ap\/index.html?iref=mpstoryview<\/a><\/p>\n<p>\u00a0<!--more--><\/p>\n<p>\u00a0Though the article indicates that actions have been taken against the manufacturers of the devices identified as being compromised, the impact of the incident will likely be far broader. Traditionally, the idea of trusted computing has relied on the fact that hardware is implicitly\u00a0trusted\u00a0upon arrival from the\u00a0vendor. Only after exposure to a user or network\u00a0does it seem possible for the hardware to be in some way compromised, and thus, if the user and network are secure, so too should the hardware.<\/p>\n<p>\u00a0In this case, such a model no longer appears valid. If the hardware from the manufacturer is infected, the safeguards afforded by proper user behavior and network protection are greatly reduced. Indeed, if extended beyond peripherals to internal computer components such as motherboards or network cards, such a threat would undermine a fundamental methodology\u00a0in computer security of starting with trusted components and building on top of them secure OS and application layers. If the very hardware on which such software runs is corrupt, no trusted foundation can exist upon which to expand.<\/p>\n<p>\u00a0Unfortunately, it seems unlikely that this problem will be solved before becoming more serious. Unless stores begin to feel an economic impact from consumer concerns, vendors with two, three, or more levels of seperation between themselves and the customer will have little incentive to prevent such security breaches.<\/p>\n<p>\u00a0Max A, David W, Travis M<\/p>\n","protected":false},"excerpt":{"rendered":"<p>While the idea of software viruses\u00a0is by no means new to those who work with computers, a new vector of attack seems to be developing in the form of hardware shipped from the manufacturer that is already infected with malware. &hellip; <a href=\"https:\/\/secblog.cs.washington.edu\/Security\/2008\/03\/16\/virus-laden-hardware-emerges\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":20,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[],"class_list":["post-207","post","type-post","status-publish","format-standard","hentry","category-current-events"],"_links":{"self":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/posts\/207","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\/20"}],"replies":[{"embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/comments?post=207"}],"version-history":[{"count":0,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/posts\/207\/revisions"}],"wp:attachment":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/media?parent=207"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/categories?post=207"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/tags?post=207"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}