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

safeApprove deprecated #167

Closed
code423n4 opened this issue Jan 25, 2022 · 2 comments
Closed

safeApprove deprecated #167

code423n4 opened this issue Jan 25, 2022 · 2 comments
Labels
1 (Low Risk) Assets are not at risk. State handling, function incorrect as to spec, issues with comments bug Something isn't working duplicate This issue or pull request already exists

Comments

@code423n4
Copy link
Contributor

Handle

sirhashalot

Vulnerability details

Impact

The OpenZeppelin SafeERC20 safeApprove() function has been deprecated, as seen in the comments of the OpenZeppelin code. Using this deprecated function can lead to unintended reverts and potentially the locking of funds. A deeper discussion on the deprecation of this function is in OZ issue #2219.

Proof of Concept

The deprecated function is found in:

Recommended Mitigation Steps

As suggested by the OpenZeppelin comment, replace safeApprove() with safeIncreaseAllowance() or safeDecreaseAllowance().

  • For line 422 of SherlockClaimManager.sol, use TOKEN.safeIncreaseAllowance(address(UMA), _amount)
  • For line 465 of SherlockClaimManager.sol, use TOKEN.safeDecreaseAllowance(address(UMA), 0)
  • For line 71 of AaveV2Strategy.sol, use want.safeIncreaseAllowance(address(lp), type(uint256).max)
@code423n4 code423n4 added 1 (Low Risk) Assets are not at risk. State handling, function incorrect as to spec, issues with comments bug Something isn't working labels Jan 25, 2022
code423n4 added a commit that referenced this issue Jan 25, 2022
@code423n4
sirhashalot issue #167
f2b5f59
@Evert0x Evert0x mentioned this issue Feb 9, 2022
Open
@Evert0x Evert0x added the duplicate This issue or pull request already exists label Feb 9, 2022
@CloudEllie
Copy link

Duplicate of #11

@CloudEllie CloudEllie marked this as a duplicate of #11 Feb 21, 2022
@jack-the-pug
Copy link
Collaborator

Dup #269

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

No branches or pull requests
4 participants
@Evert0x @code423n4 @CloudEllie @jack-the-pug