16 C
London
Thursday, August 17, 2017
Home Tags Wired Equivalent Privacy (WEP)

Tag: Wired Equivalent Privacy (WEP)

The very nature of wireless Wi-Fi networks means that hackers or criminals simply need to be located near an access point in order to eavesdrop and intercept network traffic. Poorly configured access point encryption or services that allow data to be sent without any encryption pose a serious threat to user data. Confidential data can be protected by encrypting traffic at wireless access points.
In fact, this method of protection is now considered essential for all Wi-Fi networks.

But what actually happens in practice? Is traffic always encrypted on public Wi-Fi networks? How does the situation differ from country to country? Kaspersky Security Network statistics can answer all these questions. We compared the situation with Wi-Fi traffic encryption in different countries using data from our threat database. We counted the number of reliable and unreliable networks in each country that has more than 10 thousand access points known to us (this obviously excludes Antarctica and other regions where there is not enough data to draw any conclusions). Security of Wireless Networks Using statistics from Kaspersky Security Network (KSN), we analyzed data from across the world for almost 32 million Wi-Fi hotspots accessed by the wireless adapters of KSN users. Encryption type used in public Wi-Fi hotspots across the world Approximately 24.7% of Wi-Fi hotspots in the world do not use any encryption at all.

This basically means that by using an antenna capable of sending and receiving data at 2.4 GHz, any individual located near an access point can easily intercept and store all user traffic and then browse it for data they are interested in.

Fortunately, modern online banking systems and messengers do not transfer unencrypted data.

But this is the only thing that prevents users of Wi-Fi networks with unencrypted traffic from revealing their passwords and other essential data when using an unsecure access point. The WEP (Wired Equivalent Privacy) protocol for encryption of data transferred over Wi-Fi is used by approximately 3.1% of all analyzed access points.

The protocol was the first to be created, quite a long time ago, and is now completely unreliable – it would take hackers just a few minutes to crack it.

From a data security point of view, using WEP is not much different from using open networks.

This protocol is being relegated to oblivion everywhere, but as we see from the chart above, it can still be found in use. Around three-quarters of all access points use encryption based on the Wi-Fi Protected Access (WPA) protocol family.

The protocols from this family are currently the most secure.

The effort required to hack WPA depends on its settings, including the complexity of the password set by the hotspot owner.
It is worth noting that an attempt to decipher traffic from “personal” (WPA-Personal, PSK authentication) wireless networks (with public access points) can be made by intercepting the handshakes between the access point and the device at the beginning of the session. “Corporate” versions are protected from this sort of interception because they use internal company authorization. When it comes to “personal” WPA2 attacks, the situation is similar to that of WPA and mostly depends on the strength of the password set by the hotspot owner. It is only fair to note that during a standard attack on a Wi-Fi access point, a personal computer can generate from 50 to 300 keys per second on average.
If the encryption key is strong, it will take years to hack it.
Still, no one can guarantee that the key used at a cafe will be secure and that the attacker will have nothing but a PC at their disposal. Overall, it can be said that today’s WPA/WPA2 “non-enterprise” versions are reasonably, but not absolutely, secure.
In particular, they allow brute-force and dictionary attacks.

There are ready-to-use publicly available tools (aircrack-ng and similar software) for performing such attacks, as well as a large number of manuals. Geography of Unsecured Wi-Fi Access Points Share of Wi-Fi hotspots that use unreliable WEP or do not encrypt data (by country) We would like to note that the five countries with the highest proportion of unsecured connections include Korea (47.9% of unsecured Wi-Fi access points), while France (40.14%) and the US (39.31%) rate 9th and 12th respectively in the list. Germany appears to be the most secure among Western European countries, with 84.91% of access points secured by WPA/WPA2 protocol encryption. Share of Wi-Fi hotspots that use WPA/WPA2 (by country) However, even when using an encrypted connection, you should not completely rely upon this security measure.

There are several scenarios that could compromise even well-encrypted network traffic.

These include fake access points with names that duplicate or mimic real ones (for example, TrainStation_Free or TrainStation Free) and compromised routers forwarding traffic without encryption to attackers (malware tools that infect such devices are already “in the wild”).

At any rate, taking care of your own security is a good idea. Recommendations for Users There are several simple rules that help protect personal data when using open Wi-Fi networks in cafes, hotels, airports, and other public places. Do not trust networks that are not password-protected. Even if a network requests a password, you should remain vigilant. Fraudsters can find out the network password at a coffee shop, for example, and then create a fake connection with the same password.

This allows them to easily steal personal user data. You should only trust network names and passwords given to you by employees of the establishment. To maximize your protection, turn off your Wi-Fi connection whenever you are not using it.

This will also save your battery life. We recommend disabling automatic connection to existing Wi-Fi networks too. If you are not 100% sure the wireless network you are using is secure, but you still need to connect to the internet, try to limit yourself to basic user actions such as searching for information. You should refrain from entering your login details for social networks or mail services, and definitely not perform any online banking operations or enter your bank card details anywhere. To avoid being a target for cybercriminals, you should enable the “Always use a secure connection” (HTTPS) option in your device settings.
It is recommended to enable this option when visiting any websites you think may lack the necessary protection. If possible, connect via a Virtual Private Network (VPN). With a VPN, encrypted traffic is transmitted over a protected tunnel, meaning criminals won’t be able to read your data, even if they gain access to them. And, of course, you should use dedicated security solutions.

They inform users about any potential dangers when connecting to a suspicious Wi-Fi network and prevent any passwords or other confidential data from being compromised if there is a threat. One example of a dedicated solution is the Secure Connection tool included in the latest versions of Kaspersky Internet Security and Kaspersky Total Security.

This module protects users connected to Wi-Fi networks by providing a secure encrypted connection channel.
Secure Connection can be launched manually or, depending on the settings, activated automatically when connecting to public Wi-Fi networks, when navigating to online banking and payment systems or online stores, and when communicating online (mail services, social networks, etc.).
An update for wpa_supplicant is now available for Red Hat Enterprise Linux 7. The wpa_supplicant package contains an 802.1X Supplicant with support for WEP,WPA, WPA2 (IEEE 802.11i / RSN), and various EAP authentication methods.
Itimplements key negotiation with a WPA Authenticator for client stations andcontrols the roaming and IEEE 802.11 authentication and association of the WLANdriver.For detailed information on changes in this release, see the Red Hat EnterpriseLinux 7.3 Release Notes linked from the References section.Users of wpa_supplicant are advised to upgrade to these updated packages. Red Hat Enterprise Linux Desktop (v. 7) SRPMS: wpa_supplicant-2.0-20.el7.src.rpm     MD5: 86217bd08e072a91c400e8f86eff3050SHA-256: 91b9dae5e0613fd1a00167de664c62d97557ade2dd82d1dd08493901bfcaf1f7   x86_64: wpa_supplicant-2.0-20.el7.x86_64.rpm     MD5: a881be006cc2c96ca9b5fdad1aca1de5SHA-256: 9a4f03c6a07aa836b423ac83cd830fa6f83d193ec89f5c0cae4877f47eb4ee52 wpa_supplicant-debuginfo-2.0-20.el7.x86_64.rpm     MD5: 472d7ea5eff7232d559378063cab7da7SHA-256: 5a05cc11612dbe698d6dcbc00fab9db12d1b19c68854d8aca70934819ed5b8a4   Red Hat Enterprise Linux HPC Node (v. 7) SRPMS: wpa_supplicant-2.0-20.el7.src.rpm     MD5: 86217bd08e072a91c400e8f86eff3050SHA-256: 91b9dae5e0613fd1a00167de664c62d97557ade2dd82d1dd08493901bfcaf1f7   x86_64: wpa_supplicant-2.0-20.el7.x86_64.rpm     MD5: a881be006cc2c96ca9b5fdad1aca1de5SHA-256: 9a4f03c6a07aa836b423ac83cd830fa6f83d193ec89f5c0cae4877f47eb4ee52 wpa_supplicant-debuginfo-2.0-20.el7.x86_64.rpm     MD5: 472d7ea5eff7232d559378063cab7da7SHA-256: 5a05cc11612dbe698d6dcbc00fab9db12d1b19c68854d8aca70934819ed5b8a4   Red Hat Enterprise Linux Server (v. 7) SRPMS: wpa_supplicant-2.0-20.el7.src.rpm     MD5: 86217bd08e072a91c400e8f86eff3050SHA-256: 91b9dae5e0613fd1a00167de664c62d97557ade2dd82d1dd08493901bfcaf1f7   PPC: wpa_supplicant-2.0-20.el7.ppc64.rpm     MD5: 00714ab9677aaf70ecc5b19901accd6fSHA-256: 71b67b96d4744881929f81b2a98ccdec2828297c0c5366e2e62a9eb8dd277740 wpa_supplicant-debuginfo-2.0-20.el7.ppc64.rpm     MD5: 0a7ab17e2f4f9c0aaf9aae18d96008edSHA-256: 188936eb15da18146f13a306f57b89366c54d82d1d8fa31aea86d97c20fd7332   PPC64LE: wpa_supplicant-2.0-20.el7.ppc64le.rpm     MD5: 449355d2f08c5b81a79766fb3fd60969SHA-256: 002eeb4f2d3f98fed709d7c074c39635ea6bc18bfd1a6b5a96d53b63af865d44 wpa_supplicant-debuginfo-2.0-20.el7.ppc64le.rpm     MD5: 591ac75fc6bf3bccc9e7a5b107a37b0bSHA-256: 799dbf20432ae8bf85c27ea83c7c4f80ac0c7913a112b2e415aebb99a8bfcf0d   s390x: wpa_supplicant-2.0-20.el7.s390x.rpm     MD5: 4bc32f1035c35c205fcc69aae8cc9b33SHA-256: 2cd82b2aeb4c2e66cd3d713f68ceeccd08522efcda4074404df175e2ab48457b wpa_supplicant-debuginfo-2.0-20.el7.s390x.rpm     MD5: 86d1273c486cf7bb0549442d151c6f91SHA-256: 7d47e076aae3fd4de734bbf1cc4c0905de99b7bb1648e70aa596a59b040fdefb   x86_64: wpa_supplicant-2.0-20.el7.x86_64.rpm     MD5: a881be006cc2c96ca9b5fdad1aca1de5SHA-256: 9a4f03c6a07aa836b423ac83cd830fa6f83d193ec89f5c0cae4877f47eb4ee52 wpa_supplicant-debuginfo-2.0-20.el7.x86_64.rpm     MD5: 472d7ea5eff7232d559378063cab7da7SHA-256: 5a05cc11612dbe698d6dcbc00fab9db12d1b19c68854d8aca70934819ed5b8a4   Red Hat Enterprise Linux Workstation (v. 7) SRPMS: wpa_supplicant-2.0-20.el7.src.rpm     MD5: 86217bd08e072a91c400e8f86eff3050SHA-256: 91b9dae5e0613fd1a00167de664c62d97557ade2dd82d1dd08493901bfcaf1f7   x86_64: wpa_supplicant-2.0-20.el7.x86_64.rpm     MD5: a881be006cc2c96ca9b5fdad1aca1de5SHA-256: 9a4f03c6a07aa836b423ac83cd830fa6f83d193ec89f5c0cae4877f47eb4ee52 wpa_supplicant-debuginfo-2.0-20.el7.x86_64.rpm     MD5: 472d7ea5eff7232d559378063cab7da7SHA-256: 5a05cc11612dbe698d6dcbc00fab9db12d1b19c68854d8aca70934819ed5b8a4   (The unlinked packages above are only available from the Red Hat Network) 1286965 - Do not install wpa_supplicant.service as executable1319796 - wpa_supplicant ships with <deny send_interface="..." /> dbus policy These packages are GPG signed by Red Hat for security. Our key and details on how to verify the signature are available from: