mirror of
https://github.com/openssl/openssl.git
synced 2025-01-18 13:44:20 +08:00
99ba9fd02f
In the BN_hex2bn function the number of hex digits is calculated using an int value |i|. Later |bn_expand| is called with a value of |i * 4|. For large values of |i| this can result in |bn_expand| not allocating any memory because |i * 4| is negative. This leaves ret->d as NULL leading to a subsequent NULL ptr deref. For very large values of |i|, the calculation |i * 4| could be a positive value smaller than |i|. In this case memory is allocated to ret->d, but it is insufficiently sized leading to heap corruption. A similar issue exists in BN_dec2bn. This could have security consequences if BN_hex2bn/BN_dec2bn is ever called by user applications with very large untrusted hex/dec data. This is anticipated to be a rare occurrence. All OpenSSL internal usage of this function uses data that is not expected to be untrusted, e.g. config file data or application command line arguments. If user developed applications generate config file data based on untrusted data then it is possible that this could also lead to security consequences. This is also anticipated to be a rare. Issue reported by Guido Vranken. CVE-2016-0797 Reviewed-by: Andy Polyakov <appro@openssl.org> |
||
|---|---|---|
| .. | ||
| asm | ||
| bn_add.c | ||
| bn_asm.c | ||
| bn_blind.c | ||
| bn_const.c | ||
| bn_ctx.c | ||
| bn_depr.c | ||
| bn_dh.c | ||
| bn_div.c | ||
| bn_err.c | ||
| bn_exp2.c | ||
| bn_exp.c | ||
| bn_gcd.c | ||
| bn_gf2m.c | ||
| bn_intern.c | ||
| bn_kron.c | ||
| bn_lcl.h | ||
| bn_lib.c | ||
| bn_mod.c | ||
| bn_mont.c | ||
| bn_mpi.c | ||
| bn_mul.c | ||
| bn_nist.c | ||
| bn_prime.c | ||
| bn_prime.h | ||
| bn_prime.pl | ||
| bn_print.c | ||
| bn_rand.c | ||
| bn_recp.c | ||
| bn_shift.c | ||
| bn_sqr.c | ||
| bn_sqrt.c | ||
| bn_srp.c | ||
| bn_word.c | ||
| bn_x931p.c | ||
| build.info | ||
| Makefile.in | ||
| rsaz_exp.c | ||
| rsaz_exp.h | ||
| vms-helper.c | ||