unexpected-ecrecover-null-address

The ecrecover function returns address(0) when signature verification fails or inputs are invalid. If a smart contract does not validate the recovered address against address(0), an attacker can bypass signature checks when the expected signer is also uninitialized.

To audit a smart contract, provide the Solidity source file to analyze direct ecrecover calls. The process checks for the absence of require(recovered != address(0)) and flags uninitialized signer variables that lead to exploitable conditions.

The best way to secure ecrecover signature verification is replacing direct ecrecover calls with OpenZeppelin's ECDSA.recover. This library automatically handles zero-address validation and prevents unauthorized actions from uninitialized signer variables.

Yes, you can use OpenZeppelin ECDSA.recover instead of direct ecrecover in smart contracts. It provides built-in validation against address(0), ensuring that signature verification fails safely rather than returning an exploitable uninitialized signer address.

You need to check for unexpected ecrecover null address vulnerabilities when auditing any Solidity smart contract that uses ecrecover for signature verification. This detects scenarios where uninitialized signer variables allow attackers to exploit a recovered address of address(0).