Risk
8/27/2009
03:45 PM
Connect Directly
RSS
E-Mail
50%
50%

Is Your Wi-Fi Network Open to Intrusion?

Security has been an ongoing concern among wireless LANs users since their emergence in the middle 1990s. While vendors have worked diligently to close up any holes, new ones seem to emerge on a regular period, and one is now coming to light that could impact many small and medium businesses.

Security has been an ongoing concern among wireless LANs users since their emergence in the middle 1990s. While vendors have worked diligently to close up any holes, new ones seem to emerge on a regular period, and one is now coming to light that could impact many small and medium businesses.Almost as soon as they began shipping, Wi-Fi connections were deemed insecure. Initially, the underlying security checks and encryption algorithms were simple and easy to break. The wireless LAN industry has developed a variety of different security approaches -- WEP, Wi-Fi Protected Access (WPA) and WPA 2  that have had varying levels of success. Recently, Japanese computer scientists developed a way to break WPA security in as little as one minute, which means companies wireless connections could be open to hackers.

On the plus side, the attacks do not work with any WPA 2 devices using the WPA the Advanced Encryption Standard (AES) algorithm. Such products started shipping in the summer of 2006, so newer WLAN access points, switches, and routers should be safe. However, businesses need to check all of their Wi-Fi devices, identify any WPA systems, and either upgrade them to WPA 2 or dump them. Once that process is complete, their wireless LANs should be safe  at least until the next Wi-Fi security hole is identified.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Must Reads - September 25, 2014
Dark Reading's new Must Reads is a compendium of our best recent coverage of identity and access management. Learn about access control in the age of HTML5, how to improve authentication, why Active Directory is dead, and more.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-5485
Published: 2014-09-30
registerConfiglet.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via unspecified vectors, related to the admin interface.

CVE-2012-5486
Published: 2014-09-30
ZPublisher.HTTPRequest._scrubHeader in Zope 2 before 2.13.19, as used in Plone before 4.3 beta 1, allows remote attackers to inject arbitrary HTTP headers via a linefeed (LF) character.

CVE-2012-5487
Published: 2014-09-30
The sandbox whitelisting function (allowmodule.py) in Plone before 4.2.3 and 4.3 before beta 1 allows remote authenticated users with certain privileges to bypass the Python sandbox restriction and execute arbitrary Python code via vectors related to importing.

CVE-2012-5488
Published: 2014-09-30
python_scripts.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via a crafted URL, related to createObject.

CVE-2012-5489
Published: 2014-09-30
The App.Undo.UndoSupport.get_request_var_or_attr function in Zope before 2.12.21 and 3.13.x before 2.13.11, as used in Plone before 4.2.3 and 4.3 before beta 1, allows remote authenticated users to gain access to restricted attributes via unspecified vectors.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
In our next Dark Reading Radio broadcast, we’ll take a close look at some of the latest research and practices in application security.