We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
src/crypto/crypto_ec.cc
GroupOrderSize
20.18.0
any
crypto
In function GroupOrderSize call of BignumPointer::New() can return nullptr pointer (yes its can raise error via ERR_raise).
BignumPointer::New()
ERR_raise
node/src/crypto/crypto_ec.cc
Line 939 in bf59539
After this ptr passed to EC_GROUP_get_order
EC_GROUP_get_order
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
If BignumPointer::New() return pointer that stores nullptr
Check BignumPointer::New() for nullptr
Lack of nullptr check
Additional information Found by Linux Verification Center (linuxtesting.org) with SVACE.
Reporter: Burkov Egor ([email protected]).
Organization: R-Vision ([email protected]).
The text was updated successfully, but these errors were encountered:
No branches or pull requests
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 ([email protected]).
Organization: R-Vision ([email protected]).
The text was updated successfully, but these errors were encountered: