diff options
author | Matt Caswell <matt@openssl.org> | 2016-02-22 10:27:18 +0000 |
---|---|---|
committer | Matt Caswell <matt@openssl.org> | 2016-02-29 16:32:18 +0000 |
commit | 99ba9fd02fd481eb971023a3a0a251a37eb87e4c (patch) | |
tree | 131030cfec9639b7309183ca1db2c510f2c256bc /build.info | |
parent | 15e58273da866e47832ee46ef3023beeefb870a9 (diff) |
Fix BN_hex2bn/BN_dec2bn NULL ptr/heap corruption
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>
Diffstat (limited to 'build.info')
0 files changed, 0 insertions, 0 deletions