Skip to content

Conversation

@natachigram
Copy link
Contributor

No description provided.

@guardrails
Copy link

guardrails bot commented Feb 27, 2023

⚠️ We detected 8 security issues in this pull request:

Insecure Use of Low-Level Call (6)
Docs Details
💡 Title: avoid-low-level-calls, Severity: N/A
https://github.com/chainstack/developer-hub-content/blob/97df6fa1e342355d961969345db0014f48484065/coding-articles/natachi-article-introduction-smart-contract-auditing/code/lib/forge-std/lib/ds-test/src/test.sol#L53
💡 Title: avoid-low-level-calls, Severity: N/A
https://github.com/chainstack/developer-hub-content/blob/97df6fa1e342355d961969345db0014f48484065/coding-articles/natachi-article-introduction-smart-contract-auditing/code/lib/forge-std/lib/ds-test/src/test.sol#L67
💡 Title: avoid-low-level-calls, Severity: N/A
https://github.com/chainstack/developer-hub-content/blob/97df6fa1e342355d961969345db0014f48484065/coding-articles/natachi-article-introduction-smart-contract-auditing/code/lib/forge-std/src/StdCheats.sol#L470
💡 Title: avoid-low-level-calls, Severity: N/A
https://github.com/chainstack/developer-hub-content/blob/97df6fa1e342355d961969345db0014f48484065/coding-articles/natachi-article-introduction-smart-contract-auditing/code/lib/forge-std/src/StdCheats.sol#L554
💡 Title: avoid-low-level-calls, Severity: N/A
https://github.com/chainstack/developer-hub-content/blob/97df6fa1e342355d961969345db0014f48484065/coding-articles/natachi-article-introduction-smart-contract-auditing/code/lib/forge-std/src/StdCheats.sol#L562
💡 Title: avoid-low-level-calls, Severity: N/A
https://github.com/chainstack/developer-hub-content/blob/97df6fa1e342355d961969345db0014f48484065/coding-articles/natachi-article-introduction-smart-contract-auditing/code/src/ReentrancyExample.sol#L17

More info on how to fix Insecure Use of Low-Level Call in Solidity.


Use of Insecure Function (2)
Docs Details
💡 Title: avoid-tx-origin, Severity: N/A
https://github.com/chainstack/developer-hub-content/blob/97df6fa1e342355d961969345db0014f48484065/coding-articles/natachi-article-introduction-smart-contract-auditing/code/lib/forge-std/test/StdCheats.t.sol#L312
💡 Title: avoid-tx-origin, Severity: N/A
https://github.com/chainstack/developer-hub-content/blob/97df6fa1e342355d961969345db0014f48484065/coding-articles/natachi-article-introduction-smart-contract-auditing/code/lib/forge-std/test/StdCheats.t.sol#L317

More info on how to fix Use of Insecure Function in Solidity.


👉 Go to the dashboard for detailed results.

📥 Happy? Share your feedback with us.


## Conclusion

In conclusion, smart contract auditing is crucial to ensure the safety of assets managed by smart contracts on the blockchain. Auditing can be done manually or with the use of automated tools, but in this article, the focus was on manual auditing with tools like Slither and Foundry. The need for smart contract auditing is driven by the immutable nature of smart contracts, which makes it difficult to fix security vulnerabilities once they are deployed. The auditing process involves examining the code line-by-line and identifying potential security issues, which are then documented and reported on. I hope this article has provided valuable insights on the importance of smart contract auditing and how to do it effectively. Thank you for reading. No newline at end of file
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Really, really good article @natachigram.

The article is good content wise, and I also like the technical concepts explored.
I'm sorry for being late in reviewing your draft, I was unavailable.

I'll put this top priority. Let's get this done.
I'll go over the code more carefully once more after you submit a second draft.

@Genesis3800 Genesis3800 merged commit bf4663a into chainstacklabs:master May 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants