1. 25 Feb, 2016 1 commit
    • Emilia Kasper's avatar
      CVE-2016-0798: avoid memory leak in SRP · 59a908f1
      Emilia Kasper authored
      
      
      The SRP user database lookup method SRP_VBASE_get_by_user had confusing
      memory management semantics; the returned pointer was sometimes newly
      allocated, and sometimes owned by the callee. The calling code has no
      way of distinguishing these two cases.
      
      Specifically, SRP servers that configure a secret seed to hide valid
      login information are vulnerable to a memory leak: an attacker
      connecting with an invalid username can cause a memory leak of around
      300 bytes per connection.
      
      Servers that do not configure SRP, or configure SRP but do not configure
      a seed are not vulnerable.
      
      In Apache, the seed directive is known as SSLSRPUnknownUserSeed.
      
      To mitigate the memory leak, the seed handling in SRP_VBASE_get_by_user
      is now disabled even if the user has configured a seed.
      
      Applications are advised to migrate to SRP_VBASE_get1_by_user. However,
      note that OpenSSL makes no strong guarantees about the
      indistinguishability of valid and invalid logins. In particular,
      computations are currently not carried out in constant time.
      
      Reviewed-by: default avatarRich Salz <rsalz@openssl.org>
      59a908f1
  2. 23 Feb, 2016 1 commit
  3. 19 Feb, 2016 1 commit
  4. 12 Feb, 2016 1 commit
  5. 11 Feb, 2016 1 commit
  6. 10 Feb, 2016 1 commit
  7. 28 Jan, 2016 9 commits
  8. 19 Jan, 2016 3 commits
  9. 17 Jan, 2016 1 commit
  10. 14 Jan, 2016 1 commit
  11. 10 Jan, 2016 2 commits
  12. 05 Jan, 2016 1 commit
  13. 28 Dec, 2015 1 commit
  14. 27 Dec, 2015 3 commits
  15. 22 Dec, 2015 1 commit
  16. 20 Dec, 2015 1 commit
  17. 19 Dec, 2015 6 commits
  18. 18 Dec, 2015 1 commit
  19. 16 Dec, 2015 1 commit
  20. 14 Dec, 2015 2 commits
  21. 10 Dec, 2015 1 commit