The capital pool has a method "approve", which gives permission for the TokenManager to spend a token held by it.
The documentation says it can only be called by the Token Manager, but anyone can call the function.
Anyone can call capitalPool.approve(randomToken). It does not put user funds at risk now, but might in future upgrades.
No funds are at risk because although it's a free approval, it only approves a trusted spender. Because it seems to go against the documentation and the protocol rules, I am reporting it as LOW.
Forge.
Add the onlyRelatedContracts modifier to the approve function, with TokenManager as the allowed contract.
This is at most low severity, even though giving max approvals shouldn't be permisionless, the respective tokenManager address is retrieved from the TadleFactory contract whereby the trusted guardian role is responsible for deploying such contracts as seen [here](https://github.com/Cyfrin/2024-08-tadle/blob/04fd8634701697184a3f3a5558b41c109866e5f8/src/factory/TadleFactory.sol#L68). Since the user still has to go through the PreMarkets/DeliveryPlace contracts to perform market actions, this max approval cannot be exploited.
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.