lotus/chain/sub
gammazero ca23a4406c Do not update message info cache until after message validation
The sequence number used for replay detection was being updated before message validation confirmed that the message originated from the correct host. This would allow one host A to create a message with the ID of another host B that could then update the cached sequence number for B. While the message from A would fail validation and be ignored, the cached sequence number for B would get updated. This would lead to a temporary DoS for host B as its messages were incorrectly rejected as replays.

This fixes the issue by setting the cached sequence number after message validation.
2023-08-23 14:30:22 -07:00
..
ratelimit spelling in comment 2022-02-10 11:25:30 -08:00
incoming_test.go Replace use of storetheindex with go-libipni 2023-05-17 11:41:00 -07:00
incoming.go Do not update message info cache until after message validation 2023-08-23 14:30:22 -07:00