The buyer of the ticket could be front-runned by the ticket owner who claims the rewards before the ticket's NFT is traded

`CidNFT`: Broken `tokenURI` function

Protocol fees can be withdrawn multiple times in `Erc20Quest`

DOS risk if enough tokens are minted in Quest.claim can lead, at least, to transaction fee lost

`LienToken`: Lender and liquidator can collude to block auction and seize collateral

Attacker can gain control of counterfactual wallet

Incompatibility with fee-on-transfer/inflationary/deflationary/rebasing tokens, on both base tokens and quote tokens, with varying impacts

Solmate's ERC20 does not check for token contract's existence, which opens up possibility for a honeypot attack

Owner can transfer all ERC20 reward token out using function recoverERC20

Chainlink oracle data feed is not sufficiently validated and can return stale `price`

Malicious manipulation of gas reserve can deny access to MIMOProxy

Malicious targets can manipulate MIMOProxy permissions

If a MIMOProxy owner destroys their proxy, they cannot deploy another from the same address

Untyped data signing

Project funds can be drained by reusing signatures, in some cases

Division rounding can make fraction-price lower than intended (down to zero)

Use of `payable.transfer()` may lock user funds

ORACLE DATA FEED CAN BE OUTDATED YET USED ANYWAYS WHICH WILL IMPACT ON PAYMENT LOGIC

Use a safe transfer helper library for ERC20 transfers

Unhandled chainlink revert would lock all price oracle access

Order duration can be set to 0 by Malicious maker

`fillOrder()` and `exercise()` may lock Ether sent to the contract, forever

Putty position tokens may be minted to non ERC721 receivers

Use of Solidity version 0.8.13 which has two known issues applicable to PuttyV2

The contract serves as a flashloan pool without fee

`fee` can change without the consent of users

Overpayment of native ETH is not refunded to buyer

Accumulated ETH fees of InfinityExchange cannot be retrieved

Malicious user can populate `rewards` array with tokens of their interest reaching limits of `MAX_REWARD_TOKENS`

RubiconRouter: Excess ether did not return to the user

No cap on fees can result in a DOS in BathToken.withdraw()

Use `safeTransfer()`/`safeTransferFrom()` instead of `transfer()`/`transferFrom()`

Owner can modify the feeRate on existing vaults and steal the strike value on exercise

Vaults steal rebasing tokens' rewards

Vault is Not Compatible with Fee Tokens and Vaults with Such Tokens Could Be Exploited

User's may accidentally overpay in `buyOption()` and the excess will be paid to the vault creator

SpeedBumpPriceGate: Excess ether did not return to the user

safeTransferFrom is recommended instead of transfer (1)

amount requires to be updated to contract balance increase (1)

Use of `.send()` May Revert if The Recipient's Fallback Function Consumes More Than 2300 Gas

Critical Oracle Manipulation Risk by Lender

Chainlink's latestRoundData might return stale or incorrect results

`call()` should be used instead of `transfer()` on an `address payable`

StakedCitadel: wrong setupVesting function name

Chainlink pricer is using a deprecated API