A single malformed peer-to-peer message crashes a node before any validation runs
- Severity
- Critical
- Class
- Consensus & liveness
- System
- Layer-1 node daemon
Any peer can crash any node with one crafted message, and by aiming it at block producers and seeds, stall the whole network.
Nodes gossip messages to each other constantly, and a well-behaved node treats every one as hostile until it's checked. Here a malformed field in an incoming message was handled before validation, in code that assumed the value was always in range. It wasn't, and the process died.
Because the crash happens ahead of any proof or consensus check, there's no cost or authentication in the way — a peer just sends the message.
Why it rated Critical
Unauthenticated, pre-validation, and cheap to repeat. One peer can take down individual nodes; a small flood aimed at the right nodes turns a per-node crash into a network-wide halt.
The fix class
Bound and validate untrusted fields at the very edge, before any logic touches them, and treat a decode failure as a dropped message rather than a fatal error.
