A vulnerable node is susceptible to crash when processing a maliciously crafted message from a peer, via the `snap/1` protocol. The crash can be triggered by sending a malicious `snap/1` `GetTrieNodes` package. In the `trie.TryGetNode` implementation, if the requested path is reached, the associated node will be returned, but the nilness is not checked, which can cause a panic.