Files
tor/changes
Nick Mathewson 4812441d34 Never read off the end of a buffer in base32_encode()
When we "fixed" #18280 in 4e4a7d2b0c
in 0291 it appears that we introduced a bug: The base32_encode
function can read off the end of the input buffer, if the input
buffer size modulo 5 is not equal to 0 or 3.

This is not completely horrible, for two reasons:
   * The extra bits that are read are never actually used: so this
     is only a crash when asan is enabled, in the worst case.  Not a
     data leak.

   * The input sizes passed to base32_encode are only ever multiples
      of 5. They are all either DIGEST_LEN (20), REND_SERVICE_ID_LEN
      (10), sizeof(rand_bytes) in addressmap.c (10), or an input in
      crypto.c that is forced to a multiple of 5.

So this bug can't actually trigger in today's Tor.

Closes bug 21894; bugfix on 0.2.9.1-alpha.
2017-04-07 10:47:16 -04:00
..
2016-11-07 16:19:05 -05:00
2017-02-01 10:39:48 -05:00
2016-11-06 16:39:46 -05:00
2016-10-31 15:05:56 -04:00
2016-11-06 16:39:46 -05:00
2016-11-06 16:39:46 -05:00
2016-11-07 11:01:21 -05:00
2016-11-16 13:14:03 +11:00
2016-12-01 10:14:42 -05:00
2016-12-23 08:08:14 -05:00
2017-02-07 09:27:17 -05:00
2017-01-22 18:48:22 -05:00
2016-10-18 19:35:10 -04:00