Submitted by josephdara, also found by josephdara, grearlake, Shield, MrPotatoMagic (1, 2), Aymen0909, ladboy233, iamandreiski, lanrebayode77, t0x1c, and Fassi_Security (1, 2)
The function retryMessage() is unable to handle some edge scenarios listed below.
A message is set to RETRIABLEin the processMessage when transfer fails or if the target address does not satisfy some conditions.
The issue here is, when the team attempts suspension of a message which is in a RETRIABLE state, the code does not block execution.
Same or a banned address.
This is because the proofReceipt[msgHash] which handles suspension is not checked. The addressBanned[_addr] is not checked too.
Recheck necessary details to verify that the transaction is still good to go.
Check the proofReceipt[msgHash].receivedAt and the  addressBanned[_addr]
adaki2004 (Taiko) disputed and commented:
0xean (Judge) commented:
 Note: For full discussion, see here.
