You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it's missed, cause in this file we have example of checking
result of BignumPointer::new
Refs: #56692
PR-URL: #56702Fixes: #56692
Reviewed-By: James M Snell <jasnell@gmail.com>
Version
20.18.0
Platform
Subsystem
crypto
What steps will reproduce the bug?
In function
GroupOrderSize
call ofBignumPointer::New()
can return nullptr pointer (yes its can raise error viaERR_raise
).node/src/crypto/crypto_ec.cc
Line 939 in bf59539
After this ptr passed to
EC_GROUP_get_order
node/src/crypto/crypto_ec.cc
Line 940 in bf59539
But this function don't expect that second param can be NULL
node/deps/openssl/openssl/crypto/ec/ec_lib.c
Line 443 in bf59539
After nullptr can be dereferenced here:
node/deps/openssl/openssl/crypto/bn/bn_lib.c
Line 1062 in bf59539
And in another places
How often does it reproduce? Is there a required condition?
If
BignumPointer::New()
return pointer that stores nullptrWhat is the expected behavior? Why is that the expected behavior?
Check
BignumPointer::New()
for nullptrWhat do you see instead?
Lack of nullptr check
Additional information
Additional information
Found by Linux Verification Center (linuxtesting.org) with SVACE.
Reporter: Burkov Egor (eburkov@rvision.ru).
Organization: R-Vision (support@rvision.ru).
The text was updated successfully, but these errors were encountered: