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.

Sign up for GitHub

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

Jump to bottom

Contract HolographERC20 lacks withdraw functions #52

Closed
code423n4 opened this issue Oct 20, 2022 · 2 comments
Closed

Contract HolographERC20 lacks withdraw functions #52

code423n4 opened this issue Oct 20, 2022 · 2 comments
Labels
bug Something isn't working duplicate This issue or pull request already exists edited-by-warden QA (Quality Assurance) Assets are not at risk. State handling, function incorrect as to spec, issues with clarity, syntax

Comments

@code423n4
Copy link
Contributor

code423n4 commented Oct 20, 2022 •
edited
Loading

Lines of code

https://github.com/code-423n4/2022-10-holograph/blob/f8c2eae866280a1acfdc8a8352401ed031be1373/contracts/enforcer/HolographERC20.sol#L138-L757

Vulnerability details

Impact

Contract HolographERC20 (enforcer/HolographERC20.sol#138-757) has payable functions (receive(), fallback(), etc.), but does not have a function to withdraw, therefore, every Ether sent to HolographERC20 will be lost.

Proof of Concept

Contract functions and structure illustrate the concept.

Tools Used

Slither

Recommended Mitigation Steps

Remove the payable attribute or add a withdraw function.
@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 Oct 20, 2022
code423n4 added a commit that referenced this issue Oct 20, 2022
@code423n4
cdahlheimer issue #52
9933787
@gzeoneth
Copy link
Member

Duplicate of #55

@gzeoneth gzeoneth marked this as a duplicate of #55 Oct 31, 2022
@gzeoneth gzeoneth added the duplicate This issue or pull request already exists label Oct 31, 2022
@gzeoneth gzeoneth added QA (Quality Assurance) Assets are not at risk. State handling, function incorrect as to spec, issues with clarity, syntax and removed 2 (Med Risk) Assets not at direct risk, but function/availability of the protocol could be impacted or leak value labels Nov 21, 2022
@gzeoneth
Copy link
Member

Consider with #55

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working duplicate This issue or pull request already exists edited-by-warden QA (Quality Assurance) Assets are not at risk. State handling, function incorrect as to spec, issues with clarity, syntax
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@code423n4 @gzeoneth