Submitted by 0x1f8b
Signature replay in PoolTemplate.
The redeem method of PoolTemplate verifies the data stored in incident, and the verification logic of this process is performed as following:
As can be seen, the only data related to the _insurance aretarget and insured, so as the incident has no relation with theInsurance, apparently nothing prevents a user to call insure with high amounts, after receive the incident, the only thing that prevents this from being reused is that the owner creates the incident with an _incidentTimestamp from the past.
So if an owner create a incident from the future its possible to create a new insure that could be reused by the same affected address.
Another lack of input verification that could facilitate this attack is the _span=0 in the insure method.
It is mandatory to add a check in applyCover that_incidentTimestamp is less than the current date and the span argument is greater than 0 in theinsure method.
oishun1112 (Insure) confirmed and resolved, but disagreed with severity:
oishun1112 (Insure) commented:
0xean (judge) commented:
oishun1112 (Insure) commented:
