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

FixedPricePassThruGate locked ether #146

Closed
code423n4 opened this issue May 8, 2022 · 3 comments
Closed

FixedPricePassThruGate locked ether #146

code423n4 opened this issue May 8, 2022 · 3 comments
Labels
3 (High Risk) Assets can be stolen/lost/compromised directly bug Something isn't working duplicate This issue or pull request already exists

Comments

@code423n4
Copy link
Contributor

Lines of code

https://github.com/code-423n4/2022-05-factorydao/blob/db415804c06143d8af6880bc4cda7222e5463c0e/contracts/FixedPricePassThruGate.sol#L48
https://github.com/code-423n4/2022-05-factorydao/blob/db415804c06143d8af6880bc4cda7222e5463c0e/contracts/FixedPricePassThruGate.sol#L53

Vulnerability details

Impact

Contract FixedPricePassThruGate is a pass thru gate that is passing funds to the gate's beneficiary. Function passThruGate requires to send ether that is equal or more than gate.ethCost. In the case of receiving more ether than gate.ethCost, passThruGate passes to the beneficiary only amount of gate.ethCost:

(bool sent, bytes memory data) = gate.beneficiary.call{value: gate.ethCost}("");

Since there is no way to withdraw ether it ends up with ether being locked forever in the contract and effectively loss of funds for the user(s).

Proof of Concept

FixedPricePassThruGate.sol:

Tools Used

Manual Review / VSCode

Recommended Mitigation Steps

It is recommended to either pass msg.value to beneficiary:

(bool sent, bytes memory data) = gate.beneficiary.call{value: msg.value}("");

or make sure that exact amount of ether is sent:

require(msg.value == gate.ethCost, 'Please send exact amount of ETH');
@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 8, 2022
code423n4 added a commit that referenced this issue May 8, 2022
@illuzen
Copy link
Collaborator

illuzen commented May 11, 2022

Duplicate #49

@illuzen illuzen closed this as completed May 11, 2022
@illuzen illuzen added the duplicate This issue or pull request already exists label May 11, 2022
@gititGoro gititGoro added 3 (High Risk) Assets can be stolen/lost/compromised directly and removed 2 (Med Risk) Assets not at direct risk, but function/availability of the protocol could be impacted or leak value labels Jun 14, 2022
@gititGoro
Copy link
Collaborator

Upgraded severity: lost user funds.

@gititGoro
Copy link
Collaborator

Duplicate of #48

@gititGoro gititGoro marked this as a duplicate of #48 Jun 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3 (High Risk) Assets can be stolen/lost/compromised directly bug Something isn't working duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

3 participants