<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>Security Pitfalls</title>
    <link rel="alternate" type="text/html" href="http://www.securitypitfalls.org/" />
    <link rel="self" type="application/atom+xml" href="http://www.securitypitfalls.org/atom.xml" />
    <id>tag:www.securitypitfalls.org,2009-05-10://2</id>
    <updated>2010-02-28T09:51:48Z</updated>
    
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.25</generator>

<entry>
    <title>Security is no matter of daytime</title>
    <link rel="alternate" type="text/html" href="http://www.securitypitfalls.org/2010/02/security-is-no-matte.html" />
    <id>tag:www.securitypitfalls.org,2010://2.106</id>

    <published>2010-02-28T09:17:23Z</published>
    <updated>2010-02-28T09:51:48Z</updated>

    <summary>You might say, &quot;Of course, security has to be applied 24/7&quot;, but the obvious is not the standard. An example...</summary>
    <author>
        <name>Tom</name>
        <uri>http://www.securitypitfalls.org</uri>
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://www.securitypitfalls.org/">
        <![CDATA[You might say, "Of course, security has to be applied 24/7", but the obvious is not the standard. An example was given by Sebastian Klipper on his blog "Klipper on Security: Ps(i)2 - Sicherheit in Informationssystemen". Thanks for sharing the content of his post by CC license.<div><br /></div><div><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><a href="http://www.securitypitfalls.org/assets_c/2010/02/Airport_Rome_01-443.html" onclick="window.open('http://www.securitypitfalls.org/assets_c/2010/02/Airport_Rome_01-443.html','popup','width=800,height=597,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.securitypitfalls.org/assets_c/2010/02/Airport_Rome_01-thumb-600x447-443.png" width="600" height="447" alt="Airport_Rome_01.png" class="mt-image-none" style="" /></a></span></div><div><br /></div><div>During the night, journalist Tommaso Cerno did a short trip to the airport of Rome and shared his &nbsp;experience on the web. The problem? There was no security at all. The screening lines and the security areas are freely accessible, doors secured by access codes or code cards are open, homeless people are taking a nap in the interior. Tommaso filmed the his tour through the airport and published it online:&nbsp;</div><div><br /></div><div>http://espresso.repubblica.it/multimedia/home/22897704.</div><div><br /></div><div><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><a href="http://www.securitypitfalls.org/assets_c/2010/02/Airport_Rome_02-446.html" onclick="window.open('http://www.securitypitfalls.org/assets_c/2010/02/Airport_Rome_02-446.html','popup','width=800,height=599,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.securitypitfalls.org/assets_c/2010/02/Airport_Rome_02-thumb-600x449-446.png" width="600" height="449" alt="Airport_Rome_02.png" class="mt-image-none" style="" /></a></span></div><div><br /></div><div>It would be an easy task to smuggle weapons or drugs into the airport during night. The only risk would be that one of the homeless people could find it before the next day and take it away, so Sebastian Klipper.</div><div><br /></div><div><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><a href="http://www.securitypitfalls.org/assets_c/2010/02/Airport_Rome_03-449.html" onclick="window.open('http://www.securitypitfalls.org/assets_c/2010/02/Airport_Rome_03-449.html','popup','width=800,height=591,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.securitypitfalls.org/assets_c/2010/02/Airport_Rome_03-thumb-600x443-449.png" width="600" height="443" alt="Airport_Rome_03.png" class="mt-image-none" style="" /></a></span></div><div></div>]]>
        
    </content>
</entry>

<entry>
    <title>Ever thought about asking for the master key?</title>
    <link rel="alternate" type="text/html" href="http://www.securitypitfalls.org/2010/02/ever-thought-about-a.html" />
    <id>tag:www.securitypitfalls.org,2010://2.105</id>

    <published>2010-02-10T09:05:55Z</published>
    <updated>2010-02-10T09:28:11Z</updated>

    <summary>Sebastian Klipper, Senior Information Security Consultant, recently wrote on his blog Klipper on Security about an incident he experienced in...</summary>
    <author>
        <name>Tom</name>
        <uri>http://www.securitypitfalls.org</uri>
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://www.securitypitfalls.org/">
        <![CDATA[Sebastian Klipper, Senior Information Security Consultant, recently wrote on his blog Klipper on Security about an incident he experienced in a hotel. It is quite usual to have safes in hotel rooms to store important documents. It might also be obvious that lots of these safes have master key combinations to open them in case of emergency. But, he was quite surprised as he noticed how easy it was to get the master key and that it was only 3 digits long.<div><br /></div><div><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><a href="http://www.securitypitfalls.org/assets_c/2010/02/Hotelsafe_SE_Klipper_01-437.html" onclick="window.open('http://www.securitypitfalls.org/assets_c/2010/02/Hotelsafe_SE_Klipper_01-437.html','popup','width=500,height=312,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.securitypitfalls.org/assets_c/2010/02/Hotelsafe_SE_Klipper_01-thumb-600x374-437.jpg" width="600" height="374" alt="Hotelsafe_SE_Klipper_01.jpg" class="mt-image-none" style="" /></a></span></div><div><br /></div><div>One day when he wanted to open the safe with his 4 digits code, it just responded with the message "BATTERY ERROR!". Hence, he made is way down to the reception, asking for help. The friendly receptionist went upstairs with him to have a look at the safe. After demonstrating the problem, the receptionist positioned right in front of the safe started entering a code and said:&nbsp;</div><div><br /></div><div>"Enter, 0, 0, 2, Enter, Enter."</div><div><br /></div><div><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><img alt="Hotelsafe_SE_Klipper_02.jpg" src="http://www.securitypitfalls.org/Hotelsafe_SE_Klipper_02.jpg" width="114" height="156" class="mt-image-none" style="" /></span></div><div><br /></div><div>Open! That's it and after the receptionist left, Sebastian Klipper knew the master code. Sometimes the easiest way to circumvent the security system is, ask friendly for help.<br /><div><br /></div><div>Thanks very much to Sebastian Klipper who gave us the rights to publish his story with his pictures on SecurityPitfalls.&nbsp;</div></div>]]>
        
    </content>
</entry>

<entry>
    <title>Key lesson</title>
    <link rel="alternate" type="text/html" href="http://www.securitypitfalls.org/2010/02/key-lesson.html" />
    <id>tag:www.securitypitfalls.org,2010://2.104</id>

    <published>2010-02-04T19:52:20Z</published>
    <updated>2010-02-07T14:50:22Z</updated>

    <summary>Berni sent us the following story from Steyr in Upper Austria. On a visit at the University of Applied Sciences...</summary>
    <author>
        <name>Tom</name>
        <uri>http://www.securitypitfalls.org</uri>
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://www.securitypitfalls.org/">
        <![CDATA[<div>Berni sent us the following story from Steyr in Upper Austria. On a visit at the University of Applied Sciences she found an accessible, locked room on one of the floors. The only drawback, somebody left the keys there.&nbsp;</div><div><br /></div><div><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><a href="http://www.securitypitfalls.org/assets_c/2010/02/FH_Steyr_01-431.html" onclick="window.open('http://www.securitypitfalls.org/assets_c/2010/02/FH_Steyr_01-431.html','popup','width=1536,height=2048,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.securitypitfalls.org/assets_c/2010/02/FH_Steyr_01-thumb-600x800-431.jpg" width="600" height="800" alt="FH_Steyr_01.JPG" class="mt-image-none" style="" /></a></span></div><div><br /></div><div>Now, the question is, how much value does access to this room have?&nbsp;</div><div><br /></div><div><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><a href="http://www.securitypitfalls.org/assets_c/2010/02/FH_Steyr_02-434.html" onclick="window.open('http://www.securitypitfalls.org/assets_c/2010/02/FH_Steyr_02-434.html','popup','width=1536,height=2048,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.securitypitfalls.org/assets_c/2010/02/FH_Steyr_02-thumb-600x800-434.jpg" width="600" height="800" alt="FH_Steyr_02.JPG" class="mt-image-none" style="" /></a></span></div><div><br /></div><div>First of all, you can steal paper, but that shouldn't leave too much damage to the company. Secondly, an intruder could wait for some important documents printed out. As this room is locked during the day, it could be an interesting place for getting information. Another source of information is the key itself. Even if an attacker can't get much value out of the information in the room, she could try to copy the key or just take notes about the cuts of the key. This can enable the attacker to duplicate it or use in combination with some other keys to rebuild the master key of the university's locks.</div><div><br /></div><div>So the key lesson of this story: never leave your keys unattended - and never leave it on the doors. :) Thanks to Berni for sending in this story and the pictures.&nbsp;</div><div><br /></div><div>Update (7/2/2010): Churchy added another security issue that wasn't mentioned in the blog posting above. An attacker could use the printer's network cable to get access to the network. This could be interesting especially in situations where you just have access to a secured WLAN that is separated from the internal LAN.</div>]]>
        
    </content>
</entry>

<entry>
    <title>Security in Hostels</title>
    <link rel="alternate" type="text/html" href="http://www.securitypitfalls.org/2010/01/security-in-hostels.html" />
    <id>tag:www.securitypitfalls.org,2010://2.103</id>

    <published>2010-01-01T22:00:35Z</published>
    <updated>2010-01-01T22:08:12Z</updated>

    <summary>As we&apos;ve already seen, there&apos;s very little security in hostels. Another example is given by Norb who discovered the next...</summary>
    <author>
        <name>Tom</name>
        <uri>http://www.securitypitfalls.org</uri>
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://www.securitypitfalls.org/">
        <![CDATA[As we've already seen, there's very little security in hostels. Another example is given by Norb who discovered the next few situations in a hostel in South Korea.&nbsp;<div><br /></div><div>A system that might look pretty secure for a hostel, at first, ...<br /><div><br /></div><div><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><a href="http://www.securitypitfalls.org/assets_c/2010/01/Hostel_Korea_01-419.html" onclick="window.open('http://www.securitypitfalls.org/assets_c/2010/01/Hostel_Korea_01-419.html','popup','width=480,height=640,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.securitypitfalls.org/assets_c/2010/01/Hostel_Korea_01-thumb-600x800-419.jpg" width="600" height="800" alt="Hostel_Korea_01.JPG" class="mt-image-none" style="" /></a></span></div><div><br /></div><div>... is pretty useless, if all authentication credentials are given on a sheet nearby.</div><div><br /></div><div><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><a href="http://www.securitypitfalls.org/assets_c/2010/01/Hostel_Korea_02-422.html" onclick="window.open('http://www.securitypitfalls.org/assets_c/2010/01/Hostel_Korea_02-422.html','popup','width=480,height=640,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.securitypitfalls.org/assets_c/2010/01/Hostel_Korea_02-thumb-600x800-422.jpg" width="600" height="800" alt="Hostel_Korea_02.JPG" class="mt-image-none" style="" /></a></span></div><div><br /></div><div>But it seems that the owners of the hostel are not aware of possible threats ...&nbsp;</div><div><br /></div><div><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><a href="http://www.securitypitfalls.org/assets_c/2010/01/Hostel_Korea_03-425.html" onclick="window.open('http://www.securitypitfalls.org/assets_c/2010/01/Hostel_Korea_03-425.html','popup','width=640,height=480,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.securitypitfalls.org/assets_c/2010/01/Hostel_Korea_03-thumb-600x450-425.jpg" width="600" height="450" alt="Hostel_Korea_03.JPG" class="mt-image-none" style="" /></a></span></div><div><br /></div><div>... or they are just very trustful to all the people around. :)</div><div><br /></div><div><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><a href="http://www.securitypitfalls.org/assets_c/2010/01/Hostel_Korea_04-428.html" onclick="window.open('http://www.securitypitfalls.org/assets_c/2010/01/Hostel_Korea_04-428.html','popup','width=480,height=640,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.securitypitfalls.org/assets_c/2010/01/Hostel_Korea_04-thumb-600x800-428.jpg" width="600" height="800" alt="Hostel_Korea_04.JPG" class="mt-image-none" style="" /></a></span></div><div><br /></div></div>]]>
        
    </content>
</entry>

<entry>
    <title>Stupidity of guessable Access Codes</title>
    <link rel="alternate" type="text/html" href="http://www.securitypitfalls.org/2009/12/stupidity-of-guessab.html" />
    <id>tag:www.securitypitfalls.org,2009://2.94</id>

    <published>2009-12-01T11:32:30Z</published>
    <updated>2009-12-01T11:46:50Z</updated>

    <summary>During my trip through Australia I&apos;ve discovered different security and access control systems of hostels all over the country. Unfortunately,...</summary>
    <author>
        <name>Tom</name>
        <uri>http://www.securitypitfalls.org</uri>
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://www.securitypitfalls.org/">
        <![CDATA[During my trip through Australia I've discovered different security and access control systems of hostels all over the country. Unfortunately, most of them are not very secure and as a proof, I'd like to show you some of the access codes of my last hostel.<div><br /></div><div><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><a href="http://www.securitypitfalls.org/assets_c/2009/12/Hostel_AccessCode-356.html" onclick="window.open('http://www.securitypitfalls.org/assets_c/2009/12/Hostel_AccessCode-356.html','popup','width=3648,height=2736,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.securitypitfalls.org/assets_c/2009/12/Hostel_AccessCode-thumb-600x450-356.jpg" width="600" height="450" alt="Hostel_AccessCode.JPG" class="mt-image-none" style="" /></a></span></div><div><br /></div><div>Actually, these access codes are retrieved from the doors of my rooms "40" and "35" where I have slept in. "CX90" and "CI15" are the id from the floor where the rooms are located, whereas the last part is set to the last room on the floor "48" or "38". Some of my friends have slept in room 32 and got room code "C15Z32".&nbsp;</div><div><br /></div><div>As you see, the codes are not very hard to guess and offer no security for the backpackers sleeping in there. As there was no locker available, you just could hope everybody was so friendly not to steal anything while you've been out for a few drinks.</div><div><br /></div><div>Therefore, if you have access codes in place, they should never be guessable and of course, they should be changed from time to time, so that, in case somebody publishes the codes or gets access to these codes, your company still remains secure.&nbsp;</div>]]>
        
    </content>
</entry>

<entry>
    <title>Would you trust this ATM?</title>
    <link rel="alternate" type="text/html" href="http://www.securitypitfalls.org/2009/11/would-you-trust-this.html" />
    <id>tag:www.securitypitfalls.org,2009://2.91</id>

    <published>2009-11-19T12:08:14Z</published>
    <updated>2009-11-19T13:39:20Z</updated>

    <summary>Looks good from the front...... but would you use it after you&apos;ve seen that it&apos;s unprotected from the back?I haven&apos;t...</summary>
    <author>
        <name>Tom</name>
        <uri>http://www.securitypitfalls.org</uri>
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://www.securitypitfalls.org/">
        <![CDATA[Looks good from the front...<div><br /></div><div><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><a href="http://www.securitypitfalls.org/assets_c/2009/11/ATM_01-337.html" onclick="window.open('http://www.securitypitfalls.org/assets_c/2009/11/ATM_01-337.html','popup','width=2736,height=3648,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.securitypitfalls.org/assets_c/2009/11/ATM_01-thumb-600x800-337.jpg" width="600" height="800" alt="ATM_01.JPG" class="mt-image-none" style="" /></a></span></div><div><br /></div><div><div>... but would you use it after you've seen that it's unprotected from the back?</div><div><br /></div></div><div><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><a href="http://www.securitypitfalls.org/assets_c/2009/11/ATM_02-340.html" onclick="window.open('http://www.securitypitfalls.org/assets_c/2009/11/ATM_02-340.html','popup','width=2736,height=3648,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.securitypitfalls.org/assets_c/2009/11/ATM_02-thumb-600x800-340.jpg" width="600" height="800" alt="ATM_02.JPG" class="mt-image-none" style="" /></a></span></div><div><br /></div><div>I haven't thought too much about ATM security before, but it doesn't look very trustworthy, does it?</div>]]>
        
    </content>
</entry>

<entry>
    <title>Trustful Austria</title>
    <link rel="alternate" type="text/html" href="http://www.securitypitfalls.org/2009/11/trustful-austria.html" />
    <id>tag:www.securitypitfalls.org,2009://2.85</id>

    <published>2009-11-08T05:35:05Z</published>
    <updated>2009-11-08T05:48:52Z</updated>

    <summary>Thanks to Berni, who sent us the following pictures from the Beachvolleyball Grand Slam in Klagenfurt. Impressingl, these pictures have...</summary>
    <author>
        <name>Tom</name>
        <uri>http://www.securitypitfalls.org</uri>
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://www.securitypitfalls.org/">
        <![CDATA[Thanks to Berni, who sent us the following pictures from the Beachvolleyball Grand Slam in Klagenfurt. Impressingl, these pictures have been taken in 2 subsequent years - 2007 and 2008 - and nothing has ever changed.&nbsp;<div><br /></div><div>Have you already recognised the issue in this picture?</div><div><br /></div><div><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><a href="http://www.securitypitfalls.org/assets_c/2009/11/Grand_slam_1_2007-314.html" onclick="window.open('http://www.securitypitfalls.org/assets_c/2009/11/Grand_slam_1_2007-314.html','popup','width=2048,height=1536,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.securitypitfalls.org/assets_c/2009/11/Grand_slam_1_2007-thumb-600x450-314.jpg" width="600" height="450" alt="Grand_slam_1_2007.JPG" class="mt-image-none" style="" /></a></span></div><div><br /></div><div>It's really impressive, that you can still leave your keys at your bike in Austria, but I wouldn't recommend that. :)</div><div><br /></div><div><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><a href="http://www.securitypitfalls.org/assets_c/2009/11/Grand_slam_2_2007-317.html" onclick="window.open('http://www.securitypitfalls.org/assets_c/2009/11/Grand_slam_2_2007-317.html','popup','width=2048,height=1536,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.securitypitfalls.org/assets_c/2009/11/Grand_slam_2_2007-thumb-600x450-317.jpg" width="600" height="450" alt="Grand_slam_2_2007.JPG" class="mt-image-none" style="" /></a></span></div><div><br /></div><div>One year later, at nearly the same spot, at the same time, at the same event - people haven't learned anything.&nbsp;</div><div><br /></div><div><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><a href="http://www.securitypitfalls.org/assets_c/2009/11/Grand_slam_3_2008-320.html" onclick="window.open('http://www.securitypitfalls.org/assets_c/2009/11/Grand_slam_3_2008-320.html','popup','width=2048,height=1536,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.securitypitfalls.org/assets_c/2009/11/Grand_slam_3_2008-thumb-600x450-320.jpg" width="600" height="450" alt="Grand_slam_3_2008.JPG" class="mt-image-none" style="" /></a></span></div><div><br /></div><div>As long as nothing happens, all seems to be fine, but don't get upset, when someone steals your bike.</div>]]>
        
    </content>
</entry>

<entry>
    <title>Configured to leak data</title>
    <link rel="alternate" type="text/html" href="http://www.securitypitfalls.org/2009/10/configured-to-leak-d.html" />
    <id>tag:www.securitypitfalls.org,2009://2.82</id>

    <published>2009-10-30T08:19:16Z</published>
    <updated>2009-10-30T17:21:13Z</updated>

    <summary>The Stellenwerk Newsletter of the University of Hamburg was leaking data from some of their users. Because of a configuration...</summary>
    <author>
        <name>Tom</name>
        <uri>http://www.securitypitfalls.org</uri>
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://www.securitypitfalls.org/">
        <![CDATA[The Stellenwerk Newsletter of the University of Hamburg was leaking data from some of their users. Because of a configuration error the mailing list relayed replys to their e-mails to all subscribed users. Unsubscribe messages and advertisement were spread over the mailinglist within this period of time. The responsible persons apologised for the inconvenience caused and already fixed the problem.<div><br /></div><div>The original e-mail in German:</div><div><span class="Apple-style-span" style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; "><div><div style="border-right-style: none; border-bottom-style: none; border-left-style: none; border-width: initial; border-color: initial; border-top-style: solid; border-top-color: rgb(181, 196, 223); border-top-width: 1pt; padding-top: 3pt; padding-right: 0cm; padding-bottom: 0cm; padding-left: 0cm; "><p class="MsoNormal" style="margin-right: 0cm; margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', serif; margin-top: 0cm; margin-bottom: 0.0001pt; "><span lang="EN-US" style="font-size: 10pt; font-family: Tahoma, sans-serif; "><b>Subject:</b>&nbsp;<span class="SpellE">Entschuldigung</span>&nbsp;<span class="SpellE">vom</span>&nbsp;<span class="SpellE">Stellenwerk</span><o:p></o:p></span></p></div></div><p class="MsoNormal" style="margin-right: 0cm; margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', serif; margin-top: 0cm; margin-bottom: 0.0001pt; "><span lang="EN-US"><o:p>&nbsp;</o:p></span></p><div><p class="MsoNormal" style="margin-right: 0cm; margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', serif; margin-top: 0cm; margin-bottom: 0.0001pt; "><span style="font-size: 10pt; font-family: Arial, sans-serif; ">Sehr geehrte Damen und Herren,<o:p></o:p></span></p><p class="MsoNormal" style="margin-right: 0cm; margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', serif; margin-top: 0cm; margin-bottom: 0.0001pt; "><span style="font-size: 10pt; font-family: Arial, sans-serif; ">&nbsp;<o:p></o:p></span></p><p class="MsoNormal" style="margin-right: 0cm; margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', serif; margin-top: 0cm; margin-bottom: 0.0001pt; "><span style="font-size: 10pt; font-family: Arial, sans-serif; ">unsere gestrige E-Mail an Sie und andere Kunden hatte aufgrund eines Systemfehlers unangenehme Folgen: Einige Antworten wurden nicht nur an uns, sondern an andere Empfänger gesendet. So sind sie eventuell auch in Ihrem Postfach gelandet.<o:p></o:p></span></p><p class="MsoNormal" style="margin-right: 0cm; margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', serif; margin-top: 0cm; margin-bottom: 0.0001pt; "><span style="font-size: 10pt; font-family: Arial, sans-serif; ">&nbsp;<o:p></o:p></span></p><p class="MsoNormal" style="margin-right: 0cm; margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', serif; margin-top: 0cm; margin-bottom: 0.0001pt; "><span style="font-size: 10pt; font-family: Arial, sans-serif; ">Dafür möchten wir uns bei Ihnen entschuldigen und können Ihnen versichern, dass der Fehler mittlerweile behoben werden konnte und dass es nicht wieder vorkommen wird.<o:p></o:p></span></p><p class="MsoNormal" style="margin-right: 0cm; margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', serif; margin-top: 0cm; margin-bottom: 0.0001pt; "><span style="font-size: 10pt; font-family: Arial, sans-serif; ">&nbsp;<o:p></o:p></span></p><p class="MsoNormal" style="margin-right: 0cm; margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', serif; margin-top: 0cm; margin-bottom: 0.0001pt; "><span style="font-size: 10pt; font-family: Arial, sans-serif; ">Wir sind alle sehr betroffen und hoffen, dass Sie auch zukünftig unseren Service gerne nutzen.<o:p></o:p></span></p><p class="MsoNormal" style="margin-right: 0cm; margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', serif; margin-top: 0cm; margin-bottom: 0.0001pt; "><span style="font-size: 10pt; font-family: Arial, sans-serif; ">&nbsp;<o:p></o:p></span></p><p class="MsoNormal" style="margin-right: 0cm; margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', serif; margin-top: 0cm; margin-bottom: 0.0001pt; "><span style="font-size: 10pt; font-family: Arial, sans-serif; ">Wir bitten um Ihr Verständnis und verbleiben&nbsp;&nbsp;<o:p></o:p></span></p><p class="MsoNormal" style="margin-right: 0cm; margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', serif; margin-top: 0cm; margin-bottom: 0.0001pt; "><span style="font-size: 10pt; font-family: Arial, sans-serif; ">mit freundlichen Grüßen</span></p></div><p style="margin-right: 0cm; margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 10pt; font-family: Arial, sans-serif; ">xxxxx xxxxxxxx&nbsp;<br />Leitung Stellenwerk&nbsp;<br />_______________________________________</span><o:p></o:p></p><div><font class="Apple-style-span" face="Arial, sans-serif" size="3"><span class="Apple-style-span" style="font-size: 13px;"><br /></span></font></div><div><font class="Apple-style-span" face="Arial, sans-serif" size="3"><span class="Apple-style-span" style="font-size: 13px;">Thanks to Sup for reporting this incindent.</span></font></div></span></div>]]>
        
    </content>
</entry>

<entry>
    <title>Not even Security by Obscurity</title>
    <link rel="alternate" type="text/html" href="http://www.securitypitfalls.org/2009/10/not-even-security-by.html" />
    <id>tag:www.securitypitfalls.org,2009://2.78</id>

    <published>2009-10-16T01:34:57Z</published>
    <updated>2009-10-16T02:00:44Z</updated>

    <summary><![CDATA[Got the link to this image from vmorbit - thanks for your contribution to the project.&nbsp;Is this really working?&nbsp;Can't add...]]></summary>
    <author>
        <name>Tom</name>
        <uri>http://www.securitypitfalls.org</uri>
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://www.securitypitfalls.org/">
        <![CDATA[Got the link to this image from vmorbit - thanks for your contribution to the project.&nbsp;<div><br /></div><div>Is this really working?&nbsp;Can't add anything more to this - check it out yourself.&nbsp;</div><div><br /></div><div><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><a href="http://www.securitypitfalls.org/assets_c/2009/10/epic-fail-wifi-network-fail-294.html" onclick="window.open('http://www.securitypitfalls.org/assets_c/2009/10/epic-fail-wifi-network-fail-294.html','popup','width=320,height=480,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.securitypitfalls.org/assets_c/2009/10/epic-fail-wifi-network-fail-thumb-600x900-294.jpg" width="600" height="900" alt="epic-fail-wifi-network-fail.jpg" class="mt-image-none" style="" /></a></span></div><div>(c) by Cheezburger Network (Failblog.org) - pls contact them, if you want to use the image in further documents</div>]]>
        
    </content>
</entry>

<entry>
    <title>Unattended Working Places - Part 1</title>
    <link rel="alternate" type="text/html" href="http://www.securitypitfalls.org/2009/10/unattended-working-p.html" />
    <id>tag:www.securitypitfalls.org,2009://2.71</id>

    <published>2009-10-09T03:21:52Z</published>
    <updated>2009-10-09T03:36:01Z</updated>

    <summary>Our unattended series goes on and this time we discovered an unattended working place at the airport in Munich. At...</summary>
    <author>
        <name>Tom</name>
        <uri>http://www.securitypitfalls.org</uri>
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://www.securitypitfalls.org/">
        <![CDATA[Our unattended series goes on and this time we discovered an unattended working place at the airport in Munich. At first, I was not really shure what was going on, should have people really left the place unattended or was she just around the corner?<div><br /></div><div><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><a href="http://www.securitypitfalls.org/assets_c/2009/10/Unattended_WP_Munich_01-261.html" onclick="window.open('http://www.securitypitfalls.org/assets_c/2009/10/Unattended_WP_Munich_01-261.html','popup','width=1632,height=1224,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.securitypitfalls.org/assets_c/2009/10/Unattended_WP_Munich_01-thumb-600x450-261.jpg" width="600" height="450" alt="Unattended_WP_Munich_01.JPG" class="mt-image-none" style="" /></a></span></div><div><br /></div><div>But, indeed, after 5 minutes of waiting, no one was showing up and the blue sign on the desk saying "Be right back." seemed to be there for a reason. I took a second, closer picture of the working place, noticing that all the screens were not locked and paper sheets were lying on the desk.&nbsp;</div><div><br /></div><div><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><a href="http://www.securitypitfalls.org/assets_c/2009/10/Unattended_WP_Munich_02-264.html" onclick="window.open('http://www.securitypitfalls.org/assets_c/2009/10/Unattended_WP_Munich_02-264.html','popup','width=1632,height=1224,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.securitypitfalls.org/assets_c/2009/10/Unattended_WP_Munich_02-thumb-600x450-264.jpg" width="600" height="450" alt="Unattended_WP_Munich_02.JPG" class="mt-image-none" style="" /></a></span></div><div><br /></div><div>Apart from the possibility that an attacker could exploit this situation to try to get access to the systems, it may have been enough for an attacker to study all the information presented to him by the paper sheets and the computer screens.</div><div><br /></div><div>Therefore, companies should raise awareness for such problems and insist their employees to always lock the computer desktops when leaving the working place and to hide important working papers when there's the possibility that attackers could get advantage by reading them.&nbsp;</div>]]>
        
    </content>
</entry>

<entry>
    <title>Join the network</title>
    <link rel="alternate" type="text/html" href="http://www.securitypitfalls.org/2009/09/join-the-network.html" />
    <id>tag:www.securitypitfalls.org,2009://2.67</id>

    <published>2009-09-24T01:46:19Z</published>
    <updated>2009-09-24T02:07:32Z</updated>

    <summary>Best greets to Norb, who sent us pictures from Seoul, South Korea. He is living together with some other students...</summary>
    <author>
        <name>Tom</name>
        <uri>http://www.securitypitfalls.org</uri>
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://www.securitypitfalls.org/">
        <![CDATA[Best greets to Norb, who sent us pictures from Seoul, South Korea. He is living together with some other students in a student housing. One day, he made an interesting discovery. He found a white case in the recreation room of this house.&nbsp;<div><br /></div><div><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><a href="http://www.securitypitfalls.org/assets_c/2009/09/LanSwitch_Seoul_00-222.html" onclick="window.open('http://www.securitypitfalls.org/assets_c/2009/09/LanSwitch_Seoul_00-222.html','popup','width=2048,height=1536,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.securitypitfalls.org/assets_c/2009/09/LanSwitch_Seoul_00-thumb-600x450-222.jpg" width="600" height="450" alt="LanSwitch_Seoul_00.jpg" class="mt-image-none" style="" /></a></span></div><div><br /></div><div>After opening he found the LanSwitch of the whole floor unprotected and unlocked. Of course, Norb didn't actually connect to the switch, but an attacker could gain access to the whole network, install a sniffer and collect usernames and passwords from all students living in the dormitory.</div><div><br /></div><div><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><a href="http://www.securitypitfalls.org/assets_c/2009/09/LanSwitch_Seoul_01-225.html" onclick="window.open('http://www.securitypitfalls.org/assets_c/2009/09/LanSwitch_Seoul_01-225.html','popup','width=2048,height=1536,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.securitypitfalls.org/assets_c/2009/09/LanSwitch_Seoul_01-thumb-600x450-225.jpg" width="600" height="450" alt="LanSwitch_Seoul_01.jpg" class="mt-image-none" style="" /></a></span></div><div><br /></div><div>Additionally, there was a surveillance camera installed in the room, which was recording the entrance, but not the area around the central LAN switch.&nbsp;</div><div><br /></div><div><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><a href="http://www.securitypitfalls.org/assets_c/2009/09/LanSwitch_Seoul_02-228.html" onclick="window.open('http://www.securitypitfalls.org/assets_c/2009/09/LanSwitch_Seoul_02-228.html','popup','width=2048,height=1536,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.securitypitfalls.org/assets_c/2009/09/LanSwitch_Seoul_02-thumb-600x450-228.jpg" width="600" height="450" alt="LanSwitch_Seoul_02.jpg" class="mt-image-none" style="" /></a></span></div><div><br /></div>]]>
        
    </content>
</entry>

<entry>
    <title>Unattended Cars - Part 2</title>
    <link rel="alternate" type="text/html" href="http://www.securitypitfalls.org/2009/09/unattended-cars---pa.html" />
    <id>tag:www.securitypitfalls.org,2009://2.63</id>

    <published>2009-09-15T14:01:15Z</published>
    <updated>2009-09-15T14:24:48Z</updated>

    <summary>The unattended cars series goes into round two. Thanks to Flo, who has sent in some pictures he had taken...</summary>
    <author>
        <name>Tom</name>
        <uri>http://www.securitypitfalls.org</uri>
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://www.securitypitfalls.org/">
        <![CDATA[The unattended cars series goes into round two. Thanks to Flo, who has sent in some pictures he had taken from an unattended car in Austria. Obviously, the owner doesn't really care about the security of his transport vehicle. The rear door isn't really closed, allowing attackers easy entry into the car.<div><br /></div><div><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><a href="http://www.securitypitfalls.org/assets_c/2009/09/Unattended_Car_Part2_1-195.html" onclick="window.open('http://www.securitypitfalls.org/assets_c/2009/09/Unattended_Car_Part2_1-195.html','popup','width=1224,height=1632,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.securitypitfalls.org/assets_c/2009/09/Unattended_Car_Part2_1-thumb-600x800-195.jpg" width="600" height="800" alt="Unattended_Car_Part2_1.jpg" class="mt-image-none" style="" /></a></span></div><div><br /></div><div>A clever attacker wouldn't start opening the car right away, without investigating further, thus finding out that it isn't locked at all.</div><div><br /></div><div><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><a href="http://www.securitypitfalls.org/assets_c/2009/09/Unattended_Car_Part2_2-198.html" onclick="window.open('http://www.securitypitfalls.org/assets_c/2009/09/Unattended_Car_Part2_2-198.html','popup','width=1632,height=1224,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.securitypitfalls.org/assets_c/2009/09/Unattended_Car_Part2_2-thumb-600x450-198.jpg" width="600" height="450" alt="Unattended_Car_Part2_2.jpg" class="mt-image-none" style="" /></a></span></div><div><br /></div><div>The obvious problem in this situation is of course the unlocked car or poorly closed door. However, a much greater problem can cause the free accessable contents of this car. People tend to have keys in their cars, f.e. to the garage. Sometimes there are USB sticks for the radio that have also data from their work stored on it. Or, more simple, an attacker can find old invoices that he can use for social engineering attacks. From a corporate espionage point of view, it's an invitation to install bugging devices to gather information.</div><div><br /></div><div>I think, the main problem here is, that just a few minutes of unthoughtfulness can have long-term affects on the security of a whole company or household. So, when you leave your car open and unattended, be aware of the possible outcomes. Especially for all private people, who are reading this blog, don't be paranoid, just be aware. :)</div><div><br /></div>]]>
        
    </content>
</entry>

<entry>
    <title>Sometimes the easiest way in is through the front door</title>
    <link rel="alternate" type="text/html" href="http://www.securitypitfalls.org/2009/09/sometimes-the-easies.html" />
    <id>tag:www.securitypitfalls.org,2009://2.61</id>

    <published>2009-09-08T13:42:54Z</published>
    <updated>2009-09-08T14:11:53Z</updated>

    <summary>Thank you very much to Sup for sharing his experiences he made in a chemical company. It&apos;s a very great...</summary>
    <author>
        <name>Tom</name>
        <uri>http://www.securitypitfalls.org</uri>
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://www.securitypitfalls.org/">
        <![CDATA[<div><div>Thank you very much to Sup for sharing his experiences he made in a chemical company. It's a very great example of how companies should NOT design their entrance areas.</div><div><br /></div><div>Unbelievable, but true: This chemical company has a non-locked entrance door. The anteroom is neither staffed nor camera monitored. There is a plate with the information that this would be the status quo for the next few weeks. Nothing easier than that for visitors - they can issue an identity (visitor) card (!!!) themselves. All that you need is directly placed on the desk (even blank cards to fill in). After that you can try to open the next (main) door by lockpicking (I guess it is not so easy to use the given electronic possibility) or you'll wait until the next friendly person gets out of the main building and holds the door open for you.</div><div><br /></div><div><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><a href="http://www.securitypitfalls.org/assets_c/2009/09/WayInThroughFront_01-188.html" onclick="window.open('http://www.securitypitfalls.org/assets_c/2009/09/WayInThroughFront_01-188.html','popup','width=1600,height=1200,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.securitypitfalls.org/assets_c/2009/09/WayInThroughFront_01-thumb-600x450-188.jpg" width="600" height="450" alt="WayInThroughFront_01.jpg" class="mt-image-none" style="" /></a></span></div><div><br /></div><div><div>BTW: You'll find all telephone numbers of all staff members ready for the next social engineering attack right next to the blank ID-cards. And, something positive, the telephone was not free for numbers outside the company.</div></div></div> ]]>
        
    </content>
</entry>

<entry>
    <title>Captcha protection at its best</title>
    <link rel="alternate" type="text/html" href="http://www.securitypitfalls.org/2009/09/captcha-protection-a.html" />
    <id>tag:www.securitypitfalls.org,2009://2.58</id>

    <published>2009-09-03T16:08:43Z</published>
    <updated>2009-09-03T16:28:37Z</updated>

    <summary>Great thanks to Churchy for submitting this nice programming mistake. Unfortunately, this is not a singular case and the one...</summary>
    <author>
        <name>Tom</name>
        <uri>http://www.securitypitfalls.org</uri>
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://www.securitypitfalls.org/">
        <![CDATA[<div><div>Great thanks to Churchy for submitting this nice programming mistake. Unfortunately, this is not a singular case and the one or the other will find himself trapped into the same sort of problem. But don't bother, Churchy is explaining the pitfalls.</div><div><br /></div><div>A common way to protect web forums or blog comment areas from unwanted spam without the need of manually checking all new messages before publishing them is to include captchas. Captchas are intended to be readable by humans only, thus preventing automated bots from submitting forms with spam content. However, a mechanism intended to rise the security level can also suffer from flaws that make the mechanism useless. A german news site seen in the first picture lets users post comments and includes a captcha. The first pitfall is obvious.</div><div>&nbsp;</div><div><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><a href="http://www.securitypitfalls.org/assets_c/2009/09/captchas1-174.html" onclick="window.open('http://www.securitypitfalls.org/assets_c/2009/09/captchas1-174.html','popup','width=747,height=546,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.securitypitfalls.org/assets_c/2009/09/captchas1-thumb-600x438-174.jpg" width="600" height="438" alt="Captchas_1.jpg" class="mt-image-none" style="" /></a></span></div><div>&nbsp;</div><div>The letters and numbers in the captcha can be read easily. They look exactly like typed letters, are perfectly ordered, do not include optical noise, always have the same background, have the same size and are not rotated at all. No OCR software should have any problems in reconstructing the contents of the image. However, the second and probably even worse pitfall lies in the way the images are generated. Have a look at the source code of the site:</div><div>&nbsp;</div><div><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><a href="http://www.securitypitfalls.org/assets_c/2009/09/captchas2-177.html" onclick="window.open('http://www.securitypitfalls.org/assets_c/2009/09/captchas2-177.html','popup','width=925,height=603,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.securitypitfalls.org/assets_c/2009/09/captchas2-thumb-600x391-177.jpg" width="600" height="391" alt="Captchas_2.jpg" class="mt-image-none" style="" /></a></span></div><div>&nbsp;</div><div>Who would need to find a way to reconstruct captcha images, if all you need to know is already waiting in the source code, easy to be parsed using regular expressions? Maybe the shown web site is not quite popular and submitted spam can easily be removed again by an admin, but why would you want to include a security measure that does not add any real security value at all? However, as flawed as the shown implementation might be, it may protects against bots that to not target this specific site (and flaws) but just randomly submit forms on any web site they find. Or, as Ted Humphreys would have said: Whether this solution is appropriate depends on the risk you are facing. :-)</div><div><br /></div></div>]]>
        
    </content>
</entry>

<entry>
    <title>When the time has come to think about your keypad</title>
    <link rel="alternate" type="text/html" href="http://www.securitypitfalls.org/2009/08/the-time-has-come-to.html" />
    <id>tag:www.securitypitfalls.org,2009://2.55</id>

    <published>2009-08-29T23:48:52Z</published>
    <updated>2009-08-30T01:22:17Z</updated>

    <summary>Thanks to Norb, who mailed me the link to an interesting entry on Bruce Schneier&apos;s blog. With the permission from...</summary>
    <author>
        <name>Tom</name>
        <uri>http://www.securitypitfalls.org</uri>
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://www.securitypitfalls.org/">
        <![CDATA[<div>Thanks to Norb, who mailed me the link to an interesting entry on Bruce Schneier's blog. With the permission from Bruce Schneier we will present you his pictures from some keypads.</div><div><br /></div><div>Can you guess the right combination?</div><div><br /></div><div><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><a href="http://www.securitypitfalls.org/assets_c/2009/08/digital-lock-162.html" onclick="window.open('http://www.securitypitfalls.org/assets_c/2009/08/digital-lock-162.html','popup','width=600,height=800,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.securitypitfalls.org/assets_c/2009/08/digital-lock-thumb-600x800-162.jpg" width="600" height="800" alt="security-keypad-2.jpg" class="mt-image-none" style="" /></a></span></div><div><br /></div><div>What about this one?</div><div><br /></div><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><a href="http://www.securitypitfalls.org/assets_c/2009/08/security-keypad-159.html" onclick="window.open('http://www.securitypitfalls.org/assets_c/2009/08/security-keypad-159.html','popup','width=1200,height=1600,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.securitypitfalls.org/assets_c/2009/08/security-keypad-thumb-600x800-159.jpg" width="600" height="800" alt="security-keypad.jpg" class="mt-image-none" style="" /></a></span> <div><br /></div><div><br /></div><div>In the first picture the numbers are 1-6-8-9. Of course, someone could try out every combination, but there are combinations that are more likely than others. Perhaps you have guessed them already, the most common ones would be 1986 or 1968, perhaps depending on the age of the admin or the company. :) The second one is easier and the most likely combination is 1234.</div><div><br /></div><div>There are also some very interesting comments to the blog entry. One user said, that on some keypads you don't have to try out all the possible combinations. Just press all four numbers at the same time. After pressing a few times within a short interval the keypad will get confused and will think that the correct combination was given.</div><div><br /></div><div>Another user states that most of the locks just check the last four numbers. Therefore, by pressing the combination&nbsp;<span class="Apple-style-span" style="color: rgb(0, 0, 0); font-family: Verdana, Helvetica, sans-serif; font-size: 12px; ">123412314231243121342132413214321 an attacker would just need to press 33 times instead of 96.</span></div><div><br /></div>]]>
        
    </content>
</entry>

</feed>
