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

QA Report #102

Open
code423n4 opened this issue May 2, 2022 · 0 comments
Open

QA Report #102

code423n4 opened this issue May 2, 2022 · 0 comments
Labels
bug Something isn't working QA (Quality Assurance) Assets are not at risk. State handling, function incorrect as to spec, issues with clarity, syntax

Comments

@code423n4
Copy link
Contributor

QA (LOW RISK - NON-CRITICAL)

  • Different solidity compiler versions used. This leads to potential security flaws between deployed contracts depending on the compiler version chosen for any particular file. It also greatly increases the cost of maintenance as different compiler versions have different semantics and behavior.

  • In BalancerV2LPOracle.sol, latestRoundData() method is used, but there is no check if the return value indicates stale data.

  • The require statements in AddressProvider.sol, VaultsCore.sol , ABDKMath64x64.sol don't throw error messages on revert.
    When transactions revert, the users won't receive error messages indicating the cause of the failure.

  • transfer method is used inside the codebase. Since transfer method uses 2300 gas stipend which is not adjustable,it may likely to get broken in future in case of hardforks causing gas price changes or when calling a contract's fallback function.
    Reference Link -1, Reference Link -2

  • block.timestamp is used on many places at the scoped contracts. Hoewever, this can be manipulated by malicious miners.
    Reference

@code423n4 code423n4 added bug Something isn't working QA (Quality Assurance) Assets are not at risk. State handling, function incorrect as to spec, issues with clarity, syntax labels May 2, 2022
code423n4 added a commit that referenced this issue May 2, 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 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

1 participant