-
Notifications
You must be signed in to change notification settings - Fork 10
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
No slippage check during withdraw/deposit #451
Labels
bug
Something isn't working
downgraded by judge
Judge downgraded the risk level of this issue
duplicate-281
grade-b
Q-05
QA (Quality Assurance)
Assets are not at risk. State handling, function incorrect as to spec, issues with clarity, syntax
🤖_143_group
AI based duplicate group recommendation
sufficient quality report
This report is of sufficient quality
Comments
c4-bot-2
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
Mar 15, 2024
c4-pre-sort
added
the
sufficient quality report
This report is of sufficient quality
label
Mar 18, 2024
0xEVom marked the issue as sufficient quality report |
0xEVom marked the issue as duplicate of #281 |
c4-judge
added
downgraded by judge
Judge downgraded the risk level of this issue
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
Mar 31, 2024
jhsagd76 changed the severity to QA (Quality Assurance) |
jhsagd76 marked the issue as grade-b |
This previously downgraded issue has been upgraded by jhsagd76 |
c4-judge
added
2 (Med Risk)
Assets not at direct risk, but function/availability of the protocol could be impacted or leak value
and removed
downgraded by judge
Judge downgraded the risk level of this issue
QA (Quality Assurance)
Assets are not at risk. State handling, function incorrect as to spec, issues with clarity, syntax
labels
Apr 3, 2024
jhsagd76 changed the severity to QA (Quality Assurance) |
c4-judge
added
downgraded by judge
Judge downgraded the risk level of this issue
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
Apr 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
downgraded by judge
Judge downgraded the risk level of this issue
duplicate-281
grade-b
Q-05
QA (Quality Assurance)
Assets are not at risk. State handling, function incorrect as to spec, issues with clarity, syntax
🤖_143_group
AI based duplicate group recommendation
sufficient quality report
This report is of sufficient quality
Lines of code
https://github.com/code-423n4/2024-03-revert-lend/blob/main/src/V3Vault.sol#L877-#L917
https://github.com/code-423n4/2024-03-revert-lend/blob/main/src/V3Vault.sol#L920-#L952
Vulnerability details
Vulnerability details
The deposit/withdraw function in the V3Vault lacks a mechanism for users to express their minimum acceptable output. This deficiency exposes users to potential losses of their principal due to update of the rate
In the
_deposit()
function, amount and shares is directly converted to the other by calling_convertToAssets
/_convertToShares()
function, and it is rely onnewLendExchangeRateX96
. The update ofnewLendExchangeRateX96
can make user receive less shares/cost more amounts than they expected. This thing is similar in_withdraw()
function. This scenario also can happen when user attempts to withdraw/deposit assets and their transaction is delayed due to low gas cost/network issue/reorg/ ..., which harming userImpact
Users will loss assets due to the absence of slippage control in the withdraw/deposit function.
Tools Used
Manual review
Recommended Mitigation Steps
Add slippage checking when deposit/withdraw assets
Assessed type
Other
The text was updated successfully, but these errors were encountered: