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

getPriceFromChainlink IS NOT INSUFFICIENTLY VALIDATED #28

Closed
code423n4 opened this issue Jun 10, 2022 · 3 comments
Closed

getPriceFromChainlink IS NOT INSUFFICIENTLY VALIDATED #28

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

Comments

@code423n4
Copy link
Contributor

Lines of code

https://github.com/code-423n4/2022-06-connext/blob/main/contracts/contracts/core/connext/helpers/ConnextPriceOracle.sol#:~:text=%7D-,function%20getPriceFromChainlink(address%20_tokenAddress)%20public%20view%20returns%20(uint256,%7D,-return%200%3B

Vulnerability details

Impact

Oracle data feed is insufficiently validated. There no check for stale price. Price can be stale and lead to wrong answer that will return the wrong price

Proof of Concept

ContextPriceOracle.sol L#125

There's no checks for stale price.

Tools Used

Manuel Review

Recommended Mitigation Steps

You can use validation like:
require( answer >= 0, "Stale price");

@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 Jun 10, 2022
code423n4 added a commit that referenced this issue Jun 10, 2022
@ecmendenhall
Copy link

Duplicate of #190

@jakekidd jakekidd added the duplicate This issue or pull request already exists label Jun 24, 2022
@jakekidd
Copy link
Collaborator

dup #190

@0xleastwood
Copy link
Collaborator

Merging with #76.

@0xleastwood 0xleastwood 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 Aug 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working duplicate This issue or pull request already exists QA (Quality Assurance) Assets are not at risk. State handling, function incorrect as to spec, issues with clarity, syntax
Projects
None yet
Development

No branches or pull requests

4 participants