The _createContingentPool
function does include validation for critical pool parameters provided through the _poolParams
input. This can result in the creation of misconfigured or invalid contingent pools, which could lead to unexpected behavior, loss of funds, or compromised functionality within the DIVA protocol.
Call the _createContingentPool
function with invalid _poolParams
, such as
floor > cap
expiryTime
set to a timestamp in the past.
collateralAmount
set to 0.
gradient set to invalid vakue (e.g., or greater than 1e18).
Observe that the function proceeds without reverting
The resulting contingent pool may be created with invalid parameters, causing:
Incorrect pavoff structures.
immediate expiration, rendering the pool unusable.
Zero collateral, breaking pool mechanics.
Protocol Integrity Risk:
Invalid pools compromise the DIVA Protocol's ability to function as intended, affecting user trust and system reliability.
User Losses:
Users could unintentionally provide collateral to an unusable pool, potentially locking funds.
System Errors
Downstream functions relying on valid pool parameters may behave unpredictably.
Manual Review
Add validation checks to the _createContingentPool
function to ensure all critical parameters in _poolParams
are valid before proceeding.
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.