A protobuf/binary length field could be read as a huge value, and the
`pos + len > size` bounds check overflowed size_t and slipped past, so
vector::assign threw std::length_error. Node dispatch (pairing, etc.) was
not wrapped in a catch, so this aborted the whole process (core dump) during
--whatsapp-link after the QR refreshed.
- ProtoReader::next and the binary Decoder now use overflow-safe length
checks (len > remaining) and the decoder reads 4-byte lengths unsigned and
rejects anything larger than the frame; read_bytes rejects negatives.
- WaClient::dispatch wraps all node routing in try/catch: a bad node is
logged and skipped instead of crashing the client.
Verified: build/whatsapp_test 16/16, make lint clean, and a live
--whatsapp-link run survives the QR-refresh window with no abort.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
retoorandClaude Opus 4.8
f16c5c6ede