Normal Behavior:
The ChangeFee function allows the contract owner to update buyFee and sellFee. Normally, the function should prevent setting excessive fees that could break protocol economics.
Observed Issue:
The current implementation does not validate fee values:
Problems:
Owner can set fees arbitrarily high (e.g., 100% or more).
Could break swaps, make transactions economically unviable, or confiscate all user funds.
No event emitted, making tracking changes difficult.
Likelihood:
Only owner can call this function, limiting exposure.
Misconfiguration or malicious owner action could still exploit this.
Impact:
Fees could be set to 100% or higher, preventing swaps and user withdrawals.
Users may lose funds or pay excessive fees, breaking trust and protocol usage.
Could cause economic collapse in pools if fees exceed acceptable bounds.
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.