1. 24 May, 2019 3 commits
  2. 23 May, 2019 2 commits
  3. 22 May, 2019 3 commits
  4. 21 May, 2019 2 commits
  5. 20 May, 2019 1 commit
  6. 16 May, 2019 1 commit
  7. 09 May, 2019 1 commit
  8. 08 May, 2019 1 commit
  9. 07 May, 2019 2 commits
  10. 02 May, 2019 4 commits
  11. 30 Apr, 2019 1 commit
  12. 25 Apr, 2019 3 commits
  13. 24 Apr, 2019 1 commit
  14. 23 Apr, 2019 3 commits
  15. 19 Apr, 2019 3 commits
  16. 18 Apr, 2019 1 commit
    • Richard Levitte's avatar
      asn1parse: avoid double free · 18111b13
      Richard Levitte authored
      
      
      |str| was used for multiple conflicting purposes.  When using
      '-strictpem', it's used to uniquely hold a reference to the loaded
      payload.  However, when using '-strparse', |str| was re-used to hold
      the position from where to start parsing.
      
      So when '-strparse' and '-strictpem' are were together, |str| ended up
      pointing into data pointed at by |at|, and was yet being freed, with
      the result that the payload it held a reference to became a memory
      leak, and there was a double free conflict when both |str| and |at|
      were being freed.
      
      The situation is resolved by always having |buf| hold the pointer to
      the file data, and always and only use |str| to hold the position to
      start parsing from.  Now, we only need to free |buf| properly and not
      |str|.
      
      Fixes #8752
      
      Reviewed-by: default avatarMatthias St. Pierre <Matthias.St.Pierre@ncp-e.com>
      (Merged from https://github.com/openssl/openssl/pull/8753)
      
      (cherry picked from commit 4f29f3a29b8b416a501c7166dbbca5284b198f81)
      18111b13
  17. 16 Apr, 2019 5 commits
  18. 15 Apr, 2019 3 commits