A bug exists which allows the sh variable to be used uninitialized when sscanf returns EOF.
Observe:
A simple fix would be to explicitly test if sscanf's return value is equal to 1.
Properly handle sscanf return value in ./src/secp256k1/src/tests.c #16385
issue ghost opened this issue on July 14, 2019-
ghost commented at 4:32 AM on July 14, 2019: none
-
fanquake commented at 4:34 AM on July 14, 2019: member
Please send any issues in relation to secp256k1 to the upstream repository: https://github.com/bitcoin-core/secp256k1.
- fanquake closed this on Jul 14, 2019
- DrahtBot locked this on Dec 16, 2021
