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 #269

Open
code423n4 opened this issue Jun 2, 2022 · 1 comment
Open

QA Report #269

code423n4 opened this issue Jun 2, 2022 · 1 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

Comments

@code423n4
Copy link
Contributor

code is missing natspec and in general comments

This problem may lead into problems with readability and maintainability, also may lead into unexpected behaviours.
Reference: https://secureum.substack.com/p/security-pitfalls-and-best-practices-201?s=r
Keypoint 154: Comments

Example: https://github.com/code-423n4/2022-05-vetoken/blob/main/contracts/VE3DRewardPool.sol#L122-L132
Recommendations: Add the return types and other key aspects on the code and expected behaviours like what is supposed to do the function. Follow general guidelines for well written code like the ones from Secureum.

Reentrancy information

Reentrancy that uses transfer and transferFrom gast cost as protection may lead into problems in case gast cost changes, as can be minting more

Start of the call: https://github.com/code-423n4/2022-05-vetoken/blob/main/contracts/VeAssetDepositor.sol#L114
External call: https://github.com/code-423n4/2022-05-vetoken/blob/main/contracts/VeAssetDepositor.sol#L90

Detection: slither

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

code is missing natspec and in general comments

Valid NC

Reentrancy information

Code is non CEI conformant, valid Low

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

2 participants