Nonce Report from power cycled end node might be dropped due to duplicate detection #84

JIRA issue link

ZWAVE_SDK-2067

Commit hash

927d60f

Current Behavior

Bug Summary
When the controller initiates secured communication to a recently power cycled end device, the end device might have its sequence number randomized to previously used SN - 1, which is currently filtered by duplicate detection, and send this in the Nonce Report. ZPC will not continue the communication due to believing it to be a replay attack.

Currently ZPC ignores Nonce Report due to duplicate detection. Secure communication stops between ZPC and end node.

Expected Behavior

ZPC sends secure message with SPAN
Secure communication is successfully continued

Steps To Reproduce

1. Include always listening end node (e.g. SwitchBinary)
2. Power cycle end device
3. Initiate secure communication from the ZPC to the end node
4. Make sure that the sequence number in the Nonce Report by the end node is one less than in its previous secured message sent to the ZPC (before power off)
5. Note: it is probably an easier reproducer to explicitly send a Nonce Report from a PC Controller included under ZPC, with explicitly selected SN
6. Observe communication

Anything else?

Requirements
CC:009F.01.00.11.01B (establish SPAN before encrypted transmission)
CC:009F.01.03.11.001 (decrypt failure → return Nonce Report)
CC:009F.01.02.11.00A (establish new SPAN)
CC:009F.01.00.11.0AD (set SN to random value on startup)