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 #649
issue ghost opened this issue on July 14, 2019-
ghost commented at 4:40 AM on July 14, 2019: none
-
real-or-random commented at 8:24 AM on July 14, 2019: contributor
Good catch. Can you open a pull request to fix this?
-
ghost commented at 3:09 PM on July 14, 2019: none
Good catch. Can you open a pull request to fix this?
Done.
- unknown closed this on Jul 14, 2019
Contributors