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_rsa.h
RSACipherConfig
20.18.0
any
crypto
Default ctor of RSACipherConfig class cannot initialize field CryptoJobMode mode
CryptoJobMode mode
node/src/crypto/crypto_rsa.h
Line 85 in bf59539
Consider set default value for mode, otherwise it is undefined behavior
P.S. I learn some code uses that, looks its not critical, but will be fine to eliminate this bug
By using default ctor and access field mode
mode
Field should have default value
No default value
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:
src: add default value for RSACipherConfig mode field
56fb34f
Using default init of enum is UB Refs: nodejs#56693
No branches or pull requests
Version
20.18.0
Platform
Subsystem
crypto
What steps will reproduce the bug?
Default ctor of
RSACipherConfig
class cannot initialize fieldCryptoJobMode mode
node/src/crypto/crypto_rsa.h
Line 85 in bf59539
Consider set default value for mode, otherwise it is undefined behavior
P.S. I learn some code uses that, looks its not critical, but will be fine to eliminate this bug
How often does it reproduce? Is there a required condition?
By using default ctor and access field
mode
What is the expected behavior? Why is that the expected behavior?
Field should have default value
What do you see instead?
No default value
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: