{"id":1184,"date":"2009-03-13T16:27:25","date_gmt":"2009-03-14T00:27:25","guid":{"rendered":"http:\/\/cubist.cs.washington.edu\/Security\/?p=1184"},"modified":"2009-03-13T16:27:25","modified_gmt":"2009-03-14T00:27:25","slug":"security-review-technologys-vulnerability-to-sniffing-keystrokes-from-electromagnetic-emissions","status":"publish","type":"post","link":"https:\/\/secblog.cs.washington.edu\/Security\/2009\/03\/13\/security-review-technologys-vulnerability-to-sniffing-keystrokes-from-electromagnetic-emissions\/","title":{"rendered":"Security Review: Technology&#8217;s vulnerability to sniffing keystrokes from electromagnetic emissions."},"content":{"rendered":"<p>This vulnerability is one of the most profound in computing.\u00a0 Every computer has a connection from the keyboard to the CPU, and when signals are sent this connection acts as an antenna, transmitting a characteristic wave for each keystroke.\u00a0 Each key strike actually emits a characteristic sound wave for each key.\u00a0 Both of these facts have been used to sniff keystrokes from the air.\u00a0 Even worse, PS2 keyboards have a connection to ground which causes their characteristic waves to be sent out in the power grid as well.\u00a0 This means that an adversary could eavesdrop by plugging in a device near the victim&#8217;s computer.\u00a0 Theses forms of attacks were first realized by the US government during WWII, but the countermeasures they developed were deemed too difficult to roll-out at the time.<\/p>\n<p>Assets and security goals:<br \/>\n&#8211;Goal: Users should be able to type without having people know their keystrokes anywhere in the vicinity or through walls.<br \/>\n&#8211;Asset of concern: Assets that users should hold private but are currently vulnerable include papers, financial information, private communications, passwords, and business communications.<\/p>\n<p>Adversaries and threats:<br \/>\n&#8211;Other governments are an adversary who could be recording the keystrokes of any government official they can dedicate an antenna to.<br \/>\n&#8211;The main threat is that everything you do on your computer being tracked by an unknown third party.<\/p>\n<p>Potential Weaknesses:<br \/>\n&#8211;Electromagnetic waves emitted by the keyboard to computer connection cause characteristic waves to be sent with each keystroke.<br \/>\n&#8211;Connections to ground propagate characteristic signals of each keystroke in the power grid.<\/p>\n<p>Potential Defenses:<br \/>\n&#8211;Shield the keyboard-computer connection with lead.<br \/>\n&#8211;The output of all electrical lines should be filtered by some bandpass filter.<\/p>\n<p>The main difficulty with the shielding of electromagnetic radiation is that it requires a thick metal to encase the machine, which is costly, bulky, and inconvenient.\u00a0 New ways need to be researched to shield, filter, and mask the emissions of computers.\u00a0 Recently, the research team of Ecole Polytechnique announced they have uncovered ways to sniff keystrokes from 20 meters away with 95 percent accuracy using an antenna, oscilloscope, analog-to-digital converter, and a PC.\u00a0 They plan to present a talk about the research at the upcoming CanSecWest conference, so this vulnerability may become more ubiquitous in the near future.\u00a0 Paranoid people be afraid!<\/p>\n<p>http:\/\/www.nsa.gov\/public_info\/_files\/cryptologic_spectrum\/tempest.pdf<br \/>\nhttp:\/\/www.itworld.com\/security\/64193\/researchers-find-ways-sniff-keystrokes-thin-air<\/p>\n","protected":false},"excerpt":{"rendered":"<p>This vulnerability is one of the most profound in computing.\u00a0 Every computer has a connection from the keyboard to the CPU, and when signals are sent this connection acts as an antenna, transmitting a characteristic wave for each keystroke.\u00a0 Each &hellip; <a href=\"https:\/\/secblog.cs.washington.edu\/Security\/2009\/03\/13\/security-review-technologys-vulnerability-to-sniffing-keystrokes-from-electromagnetic-emissions\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":98,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[],"class_list":["post-1184","post","type-post","status-publish","format-standard","hentry","category-security-reviews"],"_links":{"self":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/posts\/1184","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\/98"}],"replies":[{"embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/comments?post=1184"}],"version-history":[{"count":2,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/posts\/1184\/revisions"}],"predecessor-version":[{"id":1187,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/posts\/1184\/revisions\/1187"}],"wp:attachment":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/media?parent=1184"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/categories?post=1184"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/tags?post=1184"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}