The Heartbleed OpenSSL vulnerability (http://heartbleed.com/) affects OpenSSL 1.0.1 through 1.0.1f (inclusive)

I use Amazon Elastic Load Balancer to terminate my SSL connections. Is ELB vulnerable?

  • I've been trying to get a straight answer to this one myself. This forum post implies yes, but it's not from an official source so I'm not sure how far I trust it (except that when in doubt I'd lean toward assuming compromised over secure).
    – voretaq7
    Apr 8, 2014 at 1:34
  • Is there any POC code available for exploiting this so we don't have to wait for/trust vendors' responses? Apr 8, 2014 at 2:49
  • http://possible.lv/tools/hb/ will check whether heartbeat is enabled, but can't detect the difference between patched and unpatched versions. http://filippo.io/Heartbleed/ claims to be a real POC, and it seemed to work for my case, but its server is slammed and the author hasn't posted source. Apr 8, 2014 at 3:51
  • 1
    filippo.io has now posted a "fork me on github" link on the page - github.com/FiloSottile/Heartbleed Apr 8, 2014 at 6:02

1 Answer 1


Update 09/04/2014 1:00AM EST

Amazon has stated that all Elastic Load Balancers have been updated and are now longer vulnerable. They recommend rotating certs as well.

Update 08/04/2014 2:56PM CST

Amazon has stated that all Elastic Load Balancers except those in US-EAST-1 have been updated, and the vast majority of those in US-EAST-1 have been updated.

Update 08/04/2014 9:58PM PST

Amazon has confirmed that this affects the ELB platform and is currently working to mitigate the exploit. See the link below for the official response.

Yes, It is. most likely. Several people have stated that they've gotten responses from Amazon that ELB is affected by this issue. Frankly most SSL applications are affected by this with the notable exception of Cloudflare who seems to have gotten early warning.

Evidence suggesting as such:


See also:



You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .