Security Summer School

User Tools

Site Tools

session:extra:heartbleed-poc

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
session:extra:heartbleed-poc [2017/06/17 15:52] – ↷ Page moved and renamed from session:12_hb to session:extra:heartbleed-poc Razvan Deaconescusession:extra:heartbleed-poc [2020/07/19 09:49] (current) – external edit 127.0.0.1
Line 1: Line 1:
-= 0x0Cb. Heartbleed Proof of Concept+====== 0x0Cb. Heartbleed Proof of Concept ======
  
-== Information Leak+===== Information Leak =====
  
 In the context of binary exploitation, information leakage attacks are based on bugs such as integers overflows, or unchecked bounds, and can be used to leak the memory contents of a process. Using this kind of attack we can overcome some protection mechanism that we just studied. We could leak stack canaries and then use them to successfully overflow the stack, or we could leak addresses from the stack or other structures, thus defeating ASLR. In the context of binary exploitation, information leakage attacks are based on bugs such as integers overflows, or unchecked bounds, and can be used to leak the memory contents of a process. Using this kind of attack we can overcome some protection mechanism that we just studied. We could leak stack canaries and then use them to successfully overflow the stack, or we could leak addresses from the stack or other structures, thus defeating ASLR.
Line 14: Line 14:
  
 This section will go through a Proof-of-Concept exploit that will enable us to leak a normal user's session cookie for a vulnerable server (localhost). This section will go through a Proof-of-Concept exploit that will enable us to leak a normal user's session cookie for a vulnerable server (localhost).
-== Environment Setup+===== Environment Setup =====
  
 To setup a minimal environment, we need a vulnerable OpenSSL version and a webserver. We also need to configure a basic website that will just serve a static page. To setup a minimal environment, we need a vulnerable OpenSSL version and a webserver. We also need to configure a basic website that will just serve a static page.
  
-=== Download Nginx & OpenSSL+==== Download Nginx & OpenSSL ====
  
   * [[https://www.openssl.org/source/openssl-1.0.1f.tar.gz|OpenSSL 1.0.1f Source]]   * [[https://www.openssl.org/source/openssl-1.0.1f.tar.gz|OpenSSL 1.0.1f Source]]
   * [[http://nginx.org/download/nginx-1.6.0.tar.gz|Nginx 1.6.0 Source]]   * [[http://nginx.org/download/nginx-1.6.0.tar.gz|Nginx 1.6.0 Source]]
  
-=== Compile Nginx & vulnerable OpenSSL+==== Compile Nginx & vulnerable OpenSSL ====
  
 <code bash> <code bash>
Line 72: Line 72:
 </code> </code>
  
-=== Basic SSL website+==== Basic SSL website ====
  
 Prepare a self-signed certificate: Prepare a self-signed certificate:
Line 130: Line 130:
 You should see the page live at https://127.0.0.1:11443. Ignore the certificate warning. You should see the page live at https://127.0.0.1:11443. Ignore the certificate warning.
  
-== Vulnerability+===== Vulnerability =====
  
 General information about this vulnerability can be obtained from [[http://heartbleed.com/|this website]]. General information about this vulnerability can be obtained from [[http://heartbleed.com/|this website]].
Line 180: Line 180:
 If the attacker sends a ''payload'', but a bogus, big, ''payload_length'', the vulnerable routine will copy past the end of the buffer and leak memory contents. Since the ''payload_length'' field is represented on 2 bytes, 64KB can be leaked. If the attacker sends a ''payload'', but a bogus, big, ''payload_length'', the vulnerable routine will copy past the end of the buffer and leak memory contents. Since the ''payload_length'' field is represented on 2 bytes, 64KB can be leaked.
  
-== Exploit+===== Exploit =====
  
 A TLS channel is established after the initial handshake part of the protocol. Since the Heartbeat RFC specifies the a Heartbeat Request can be send at any time, we simply have to initiate a TLS connection with a ''ClientHello'' message (first step of the handshake), and the send the bogus Heartbeat Request. A TLS channel is established after the initial handshake part of the protocol. Since the Heartbeat RFC specifies the a Heartbeat Request can be send at any time, we simply have to initiate a TLS connection with a ''ClientHello'' message (first step of the handshake), and the send the bogus Heartbeat Request.
session/extra/heartbleed-poc.1497714739.txt.gz · Last modified: by Razvan Deaconescu