Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Heartbleed && Wireless

33,201 views

Published on

New attack vectors for heartbleed: Enterprise wireless (and wired) networks.

This talk exposes a relatively obscure use of the heartbleed flaw: exploiting EAP-PEAP | EAP-TLS | EAP-TTLS network authentication protocols.

Update (02-06-2014): This blog post gives out more details and contains links to the cupid patch.
http://www.sysvalue.com/heartbleed-cupid-wireless/

Published in: Technology, Business
  • Dating direct: ❶❶❶ http://bit.ly/2u6xbL5 ❶❶❶
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Dating for everyone is here: ♥♥♥ http://bit.ly/2u6xbL5 ♥♥♥
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • > I'm aware that attentive developers like the people at Freeradius and Jouni Malinen were able to spot and fix the vulnerability in time. But that doesn't matter if there is no public awareness of the issue, as the patches/upgrades won't trickle down in a timely manner.

    All of the major distributions were notified, and upgraded their packages. They in turn notified all of their customers.

    There WAS massive awareness. All of the Telcos I'm in contact with were notified. All of the universities were notified, and the vulnerable ones told to upgrade.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Alan,

    My presentation and code is not an attack on any tools using OpenSSL, it's a call of attention to a vulnerability that was previously known about by attentive developers. I'm sorry some news sources (and developers) read it otherwise.

    The attack method however *is* new -- Up until now there were no publicly available tools that would trigger the heartbleed vulnerability via EAP. And the public availability of such tools -- and the attention they get -- is what prompts integrators of network products (and end customers) to upgrade to the latest (and patched) tools and libraries.

    I'm aware that attentive developers like the people at Freeradius and Jouni Malinen were able to spot and fix the vulnerability in time. But that doesn't matter if there is no public awareness of the issue, as the patches/upgrades won't trickle down in a timely manner.

    Best regards,

    LG
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • The 'new' attack method is no such thing. We (FreeRADIUS) worked together with Jouni Malinen (Hostap, who did most of the work) to valid the heartbleed issue and the fixes. We announced that we were vulnerable, and released fixes. This information has been available for about a month on http://freeradius.org.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

Heartbleed && Wireless

  1. 1. HEARTBLEED && WIRELESS New attack vectors for heartbleed: Enterprise wireless (and wired) networks Luis Grangeia lgrangeia@sysvalue.com | twitter.com/lgrangeia 28 / 05 / 2014 @ Confraria IT Security - Lisbon
  2. 2. WHAT IS HEARTBLEED “Catastrophic bug” on OpenSSL: "The Heartbleed bug allows anyone on the Internet to read the memory of the systems protected by the vulnerable versions of the OpenSSL software. This compromises the secret keys used to identify the service providers and to encrypt the traffic, the names and passwords of the users and the actual content. This allows attackers to eavesdrop communications, steal data directly from the services and users and to impersonate services and users. “On the scale of 1 to 10, this is an 11.” - Schneier
  3. 3. source: xkcd.com
  4. 4. source: xkcd.com
  5. 5. WHAT IS “ENTERPRISE WIRELESS” •WPA / WPA2 Networks •Protected by multiuser authentication •Tipically using a EAP Method: •EAP-PEAP •EAP-TTLS / EAP-TLS •EAP-SIM / EAP-AKA
  6. 6. EAP AND TLS •EAP-PEAP, EAP-TTLS, EAP-TLS •All these use a TLS tunnel over EAP to secure some part of the authentication process •EAP... OpenSSL... Heartbleed...
  7. 7. + = ?
  8. 8. SAY HELLO TO “CUPID”
  9. 9. WHAT IS CUPID •cupid is a patch for wpa_supplicant and hostapd •Attempts to exploit heartbleed over EAP TLS tunneled protocols: • EAP-PEAP, EAP-TLS, EAP-TTLS •Targets both endpoints: client and server
  10. 10. RadiusAccess PointTerminal ATTACK VECTORS
  11. 11. RadiusAccess PointTerminal ATTACK VECTORS
  12. 12. ATTACK VECTORS •Option 1: Use wpa_supplicant-cupid to attack a wireless network •Option 2: Set up a fake wireless network with hostapd-cupid to attack a vulnerable terminal
  13. 13. ATTACK VECTOR 1 Evil client (wpa_supplicant-cupid) heartbleed Vulnerable Access Point
  14. 14. ATTACK VECTOR 2 Vulnerable client heartbleed Evil Access Point (hostapd-cupid)
  15. 15. TECHNICAL DETAILS •Patch is able to heartbleed at different stages: •before TLS Handshake (unencrypted!) •After TLS handshake and before application data •After application data
  16. 16. DEMO TIME
  17. 17. VULNERABLE STUFF (CONFIRMED) •wpa_supplicant • Android terminals, Linux devices •hostapd •freeradius Must (obviously) be linked to vulnerable openssl version
  18. 18. VULNERABLE STUFF (POSSIBLY) •Everything that might use openssl for EAP TLS •iPhone, iPads, OSX? •Managed Wireless Solutions: • Aruba, Trapeze, Cisco / Meraki... •Other RADIUS servers besides freeradius •Other wireless endpoints supporting EAP: • VoIP Phones, printers... •Must test everything! Or patch.
  19. 19. ENTERPRISE “WIRELESS” && “WIRED” •802.1x Wired Authentication (aka NAC) uses EAP also! •Actually, wpa_supplicant is also used on Linux to access NAC-controlled wired networks
  20. 20. CUPID AVAILABILITY •Ask me for source code in private (for damage control) •Will (maybe) wait a few days before releasing to public •Tip to vendors: do not expect responsible disclosure for an exploit to a vulnerability that’s almost 2 months old...
  21. 21. LESSONS LEARNED •OpenSSL sucks •Learned a bit more about: • TLS Protocol • EAP Protocol •Sacred cows killed: •“heartbleed can only be exploited over TCP connections” •“heartbleed can only be exploited after TLS handshake”
  22. 22. FUTURE WORK & RECOMMENDATIONS •Improve patch and test ALL the things!! •Try different wireless devices •Compile and run wpa_supplicant-cupid on Android device •Look more closely for interesting bits of memory leaked. •Patch Wireless clients & Servers!

×