Revision 361071993182c0a37d421e2ea9a1f84ec4f1ac4f authored by Matt Caswell on 19 May 2015, 12:59:47 UTC, committed by Matt Caswell on 04 June 2015, 08:26:43 UTC
A BIGNUM can have the value of -0. The function BN_bn2hex fails to account for this and can allocate a buffer one byte too short in the event of -0 being used, leading to a one byte buffer overrun. All usage within the OpenSSL library is considered safe. Any security risk is considered negligible. With thanks to Mateusz Kocielski (LogicalTrust), Marek Kroemeke and Filip Palian for discovering and reporting this issue. Reviewed-by: Tim Hudson <tjh@openssl.org> (cherry picked from commit c56353071d9849220714d8a556806703771b9269) Conflicts: crypto/bn/bn_print.c
1 parent af3aa2b
| File | Mode | Size |
|---|---|---|
| HOWTO | ||
| apps | ||
| crypto | ||
| ssl | ||
| README | -rw-r--r-- | 598 bytes |
| c-indentation.el | -rw-r--r-- | 1.6 KB |
| fingerprints.txt | -rw-r--r-- | 2.8 KB |
| openssl-shared.txt | -rw-r--r-- | 1.5 KB |
| openssl.txt | -rw-r--r-- | 45.6 KB |
| openssl_button.gif | -rw-r--r-- | 2.0 KB |
| openssl_button.html | -rw-r--r-- | 239 bytes |
| ssleay.txt | -rw-r--r-- | 276.5 KB |
| standards.txt | -rw-r--r-- | 11.8 KB |
Computing file changes ...
