[openssl-dev] Question about valgrind error in DH in 1.0.2

[John Foley]

Sorry for misinterpreting your question, my mistake.  I was able to
replicate the error. It looks like the invalid read is in code that's
compiled in when OPENSSL_BN_ASM_MONT5 is set, which is only for the
X86_64 target.  Looking at the diff of x86_64-mont5.pl between 1.0.1 and
1.0.2, there are quite a few changes.  My guess is this was introduced
in ec9cc70f72454b8d4a84247c86159613cee83b81.




On 05/13/2015 10:13 AM, Henrik Grindal Bakken wrote:
> John Foley <foleyj at cisco.com> writes:
>
>> If you add the --show-reachable option to valgrind, you can see where
>> the leaks originate.  They appear to be in the ex_data code (see
>> below).  As a side note, I see 416 bytes lost when using OpenSSL 1.0.1f
>> as well as 1.0.2a.
> Ah, I forgot to mention.  I'm not concerned about the leak, but the
> invalid read that's in 1.0.2 only.
>
> This one:
>
>>> ==14854== Invalid read of size 2
>>> ==14854== at 0x4F09198: bn_get_bits5 (in
>>> /home/henribak/src/thirdparty/openssl/libcrypto.so.1.0.0)
>>> ==14854== by 0x4F32B47: generate_key (in
>>> /home/henribak/src/thirdparty/openssl/libcrypto.so.1.0.0)
>>> ==14854==    by 0x400A30: main (in /home/henribak/tmp/dh-1.0.2)