Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

admin can lock funds #11

Closed
code423n4 opened this issue May 24, 2022 · 1 comment
Closed

admin can lock funds #11

code423n4 opened this issue May 24, 2022 · 1 comment
Labels
2 (Med Risk) Assets not at direct risk, but function/availability of the protocol could be impacted or leak value bug Something isn't working duplicate This issue or pull request already exists sponsor acknowledged Technically the issue is correct, but we're not going to resolve it for XYZ reasons

Comments

@code423n4
Copy link
Contributor

Lines of code

https://github.com/code-423n4/2022-05-rubicon/blob/8c312a63a91193c6a192a9aab44ff980fbfd7741/contracts/rubiconPools/BathHouse.sol#L216-L229

Vulnerability details

description

using the adminWriteBathToken function in BathHouse.sol, the admin can arbitrarily change the bath token address. If done maliciously can lock underlying funds of users who have deposited into that bath token

/2022-05-rubicon/contracts/rubiconPools/BathHouse.sol
216:     /// @notice A migration function that allows the admin to write arbitrarily to tokenToBathToken
217:     function adminWriteBathToken(ERC20 overwriteERC20, address newBathToken)
218:         external
219:         onlyAdmin
220:     {
221:         tokenToBathToken[address(overwriteERC20)] = newBathToken;
222:         emit LogNewBathToken(
223:             address(overwriteERC20),
224:             newBathToken,
225:             address(0),
226:             block.timestamp,
227:             msg.sender
228:         );
229:     }
@code423n4 code423n4 added 2 (Med Risk) Assets not at direct risk, but function/availability of the protocol could be impacted or leak value bug Something isn't working labels May 24, 2022
code423n4 added a commit that referenced this issue May 24, 2022
@bghughes bghughes added the sponsor acknowledged Technically the issue is correct, but we're not going to resolve it for XYZ reasons label Jun 7, 2022
@HickupHH3
Copy link
Collaborator

duplicate of #249

@HickupHH3 HickupHH3 added the duplicate This issue or pull request already exists label Jun 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2 (Med Risk) Assets not at direct risk, but function/availability of the protocol could be impacted or leak value bug Something isn't working duplicate This issue or pull request already exists sponsor acknowledged Technically the issue is correct, but we're not going to resolve it for XYZ reasons
Projects
None yet
Development

No branches or pull requests

3 participants