Skip to content
  1. Jul 19, 2017
    • Matt Caswell's avatar
      Remove some dead code · 42aebbd5
      Matt Caswell authored
      
      
      The intention of the removed code was to check if the previous operation
      carried. However this does not work. The "mask" value always ends up being
      a constant and is all ones - thus it has no effect. This check is no longer
      required because of the previous commit.
      
      Reviewed-by: default avatarRich Salz <rsalz@openssl.org>
      (Merged from https://github.com/openssl/openssl/pull/3832)
      
      (cherry picked from commit d5475e31)
      42aebbd5
    • Matt Caswell's avatar
      Fix undefined behaviour in e_aes_cbc_hmac_sha256.c and e_aes_cbc_hmac_sha1.c · 6db7d015
      Matt Caswell authored
      
      
      In TLS mode of operation the padding value "pad" is obtained along with the
      maximum possible padding value "maxpad". If pad > maxpad then the data is
      invalid. However we must continue anyway because this is constant time code.
      
      We calculate the payload length like this:
      
          inp_len = len - (SHA_DIGEST_LENGTH + pad + 1);
      
      However if pad is invalid then inp_len ends up -ve (actually large +ve
      because it is a size_t).
      
      Later we do this:
      
          /* verify HMAC */
          out += inp_len;
          len -= inp_len;
      
      This ends up with "out" pointing before the buffer which is undefined
      behaviour. Next we calculate "p" like this:
      
          unsigned char *p =
              out + len - 1 - maxpad - SHA256_DIGEST_LENGTH;
      
      Because of the "out + len" term the -ve inp_len value is cancelled out
      so "p" points to valid memory (although technically the pointer arithmetic
      is undefined behaviour again).
      
      We only ever then dereference "p" and never "out" directly so there is
      never an invalid read based on the bad pointer - so there is no security
      issue.
      
      This commit fixes the undefined behaviour by ensuring we use maxpad in
      place of pad, if the supplied pad is invalid.
      
      With thanks to Brian Carpenter for reporting this issue.
      
      Reviewed-by: default avatarRich Salz <rsalz@openssl.org>
      (Merged from https://github.com/openssl/openssl/pull/3832)
      
      (cherry picked from commit 335d0a46)
      6db7d015
  2. Jul 18, 2017
  3. Jul 17, 2017
  4. Jul 14, 2017
  5. Jul 10, 2017
  6. Jul 09, 2017
  7. Jul 07, 2017
  8. Jul 05, 2017
  9. Jul 03, 2017
  10. Jul 01, 2017
  11. Jun 29, 2017
  12. Jun 25, 2017
  13. Jun 22, 2017
  14. Jun 21, 2017
  15. Jun 20, 2017
  16. Jun 19, 2017
  17. Jun 17, 2017
  18. Jun 15, 2017
  19. Jun 14, 2017