<p>Smart contracts are difficult to change, once you launch it to the market there is no going back. This is often an unpleasant thing that can distort your desires. Developing smart contracts is nothing but the aim of making it easier and more profitable, but if it turns into a disaster, it&#8217;s not your hope.</p>
<p>You may have planned the development of a <a href="http://emveep-blog.local/blog/cost-of-hiring-smart-contract-developers/">smart contract</a> that is mature and good to avoid failure, but a good smart contract will also be difficult to do well. Three main attributes are basic in operating smart contracts, namely expressing value, transparency, and immutability.</p>
<p>However, these three attributes have also become a security hazard and a target for cybercriminals. Even in the absence of external criminals, system vulnerabilities are often the reason for the capital collapse and business losses caused by the weakness of these three attributes.</p>
<p>In this article, let&#8217;s discuss what vulnerabilities might occur in a smart contract, leading to failure, and examples of cases that have occurred in companies whose smart contracts were successfully hacked.</p>
<h2>5 Vulnerabilities of Smart Contract</h2>
<h3>1. Arithmetic Error of Integers</h3>
<p><img fetchpriority="high" decoding="async" class="aligncenter wp-image-7390 size-large" src="http://emveep-blog.local/wp-content/uploads/2022/12/Group-483-1024x596.png" alt="Arithmetic Error of Integers" width="1024" height="596" srcset="https://api.emveep.com/wp-content/uploads/2022/12/Group-483-1024x596.png 1024w, https://api.emveep.com/wp-content/uploads/2022/12/Group-483-300x175.png 300w, https://api.emveep.com/wp-content/uploads/2022/12/Group-483-768x447.png 768w, https://api.emveep.com/wp-content/uploads/2022/12/Group-483.png 1080w" sizes="(max-width: 1024px) 100vw, 1024px" /></p>
<p>A simple and common error in smart contracts is an error in integer arithmetic. This is common due to the lack of floating-point support, smart contracts generally represent values as integers. In financial programs, generally using integers to represent values requires reducing values to smaller units for accuracy. A simple example of stating the value is in cents instead of dollars is that we did not state 0.5 dollars.</p>
<p>One problem the developers have been aware of is the possibility of an integer overflow. Like the distance traveled by a car, the integer printed on the computer has a maximum value, when this value is reached the integer will return to the starting point and start from the minimum value. Developers have realized this potential problem, which could have been avoided with secure math libraries.</p>
<p>However, the problems don&#8217;t stop there as it seems the developers lacked precision when integer arithmetic was done incorrectly. For example, to find out the result of calculating 25% of 80 in integers, because there is a rounding error stating 80/100*25 will result in 0. The error here is that division is done before multiplication. This is an example of an error that often occurs in smart contracts, causing failure.</p>
<h3>2. The Block Gas Limit</h3>
<p><img decoding="async" class="aligncenter wp-image-7387 size-large" src="http://emveep-blog.local/wp-content/uploads/2022/12/Group-494-1024x582.png" alt="the block gas limit" width="1024" height="582" srcset="https://api.emveep.com/wp-content/uploads/2022/12/Group-494-1024x582.png 1024w, https://api.emveep.com/wp-content/uploads/2022/12/Group-494-300x170.png 300w, https://api.emveep.com/wp-content/uploads/2022/12/Group-494-768x436.png 768w, https://api.emveep.com/wp-content/uploads/2022/12/Group-494.png 1088w" sizes="(max-width: 1024px) 100vw, 1024px" /></p>
<p>Gas block limits are used by Ethereum to ensure that each block doesn&#8217;t grow too large. This means that each block can perform only a limited number of transactions by consuming a set amount of gas.</p>
<p>In simple terms, if a transaction uses too much gas, then the transaction will not get into trouble and will not end up being executed. While actually, this can lead to general vulnerabilities.</p>
<p>A very likely common vulnerability is that if data is stored on a resizable array and then repeat access with the same array, then transactions can easily time out and roll back. This is common in the production process where the number of items usually continues to grow.</p>
<p>This can be dangerous because contracts related to this problem generally pass the unit test and work fine with small numbers. However, as usage continues and the project grows with the amount of data increasing it will fail.</p>
<p>In this case, it can usually affect funds, making recovery impossible when using recurring payments.</p>
<h3>3. Frontrunning</h3>
<p><img decoding="async" class="aligncenter wp-image-7391 size-large" src="http://emveep-blog.local/wp-content/uploads/2022/12/Group-486-1024x611.png" alt="frontrunning smart contract failure" width="1024" height="611" srcset="https://api.emveep.com/wp-content/uploads/2022/12/Group-486-1024x611.png 1024w, https://api.emveep.com/wp-content/uploads/2022/12/Group-486-300x179.png 300w, https://api.emveep.com/wp-content/uploads/2022/12/Group-486-768x458.png 768w, https://api.emveep.com/wp-content/uploads/2022/12/Group-486.png 1080w" sizes="(max-width: 1024px) 100vw, 1024px" /></p>
<p>Frontrunning can be defined as the occupation of unconfirmed transactions and is the result of transparency on the blockchain. All unconfirmed transactions will appear in the memory pool before miners include them in the block, and interested traders can easily monitor the contents of transactions and instead “advance” transactions by paying higher fees.</p>
<p>These vulnerabilities can be easily automated and have become very common in <a href="http://emveep-blog.local/blog/financial-technology-vs-defi-the-big-market/">decentralized financial applications</a> such as smart contracts. These types of problems will require some form of refactoring or even redesigning to solve them.</p>
<h3>4. Lack of Parameters of Precondition Controls</h3>
<p><img loading="lazy" decoding="async" class="aligncenter wp-image-7392 size-large" src="http://emveep-blog.local/wp-content/uploads/2022/12/Group-487-1024x619.png" alt="lack of parameter" width="1024" height="619" srcset="https://api.emveep.com/wp-content/uploads/2022/12/Group-487-1024x619.png 1024w, https://api.emveep.com/wp-content/uploads/2022/12/Group-487-300x181.png 300w, https://api.emveep.com/wp-content/uploads/2022/12/Group-487-768x464.png 768w, https://api.emveep.com/wp-content/uploads/2022/12/Group-487.png 1080w" sizes="(max-width: 1024px) 100vw, 1024px" /></p>
<p>Forgetting to verify function parameters is often the reason certain operations are invalid. Usually, this includes the address parameter not being verified against a null address, or for example an unauthenticated user having sufficient token balance to perform a certain operation.</p>
<p>Another example is access control, where only that type of user is allowed to call or use certain functions, but verification of this is never done. This error often occurs during supervision in the design process.</p>
<p>To counteract this, it&#8217;s not a bad idea to write instructions for all functions indicating the parameters, preconditions, and operations to be performed. So that the developer will stick to the design patterns that have been made.</p>
<h3>5. Logic Bugs</h3>
<p><img loading="lazy" decoding="async" class="aligncenter wp-image-7388 size-large" src="http://emveep-blog.local/wp-content/uploads/2022/12/Group-498-1024x619.png" alt="logic bugs on smart contract" width="1024" height="619" srcset="https://api.emveep.com/wp-content/uploads/2022/12/Group-498-1024x619.png 1024w, https://api.emveep.com/wp-content/uploads/2022/12/Group-498-300x181.png 300w, https://api.emveep.com/wp-content/uploads/2022/12/Group-498-768x464.png 768w, https://api.emveep.com/wp-content/uploads/2022/12/Group-498.png 1080w" sizes="(max-width: 1024px) 100vw, 1024px" /></p>
<p>The 4 vulnerabilities we&#8217;ve covered may be more specific to smart contracts, to a point that will now stick more to programming. However, fundamental errors are common in smart contract logic. This error can occur due to a simple typographical error or also a specification misunderstanding which in turn has a serious impact on security.</p>
<p>These vulnerabilities may exist which are simple errors, but they may be the first step towards the failure of smart contracts in your business. In the following, we will discuss cases of failure as well as hacking of smart contracts that have occurred.</p>
<h2>Failure and Hacking Cases on Smart Contracts</h2>
<h3>1. Axie Infinity Hacked for $620 Million</h3>
<p>The incident started with a fake job offer from North Korean hackers to a game developer that ended up being hacked which caused Axie Infinity to be willing to bear a loss of $620 million in crypto. This attack took place in March 2022 and managed to land in a game that was currently very popular and growing rapidly, namely Sky Mavis.</p>
<p>According to a recent report from <a href="https://www.theblock.co/post/156038/how-a-fake-job-offer-took-down-the-worlds-most-popular-crypto-game">digital asset news publication The Block</a>, it found that the hacker attack started with a fake job offer to staff at Sky Mavis via LinkedIn, the hacker pretending to be a company looking to hire them.</p>
<p>A senior engineer at Axie Infinity was offered such a generous salary that he showed interest in the fake job offer and has gone through several rounds of job interviews. At one point, the engineer received a PDF file detailing the job he was offered. However, the document is a way for hackers to break into the Ronin system – the Ethereum-related sidechain that powers video games based on the non-fungible Axie Infinity token.</p>
<p>The employee downloaded and opened the file on the company&#8217;s computer until the infection chain started which eventually caused huge losses and had to be borne by Axie Infinity to replace the money of the players affected by the hack.</p>
<p>The FBI has been able to link the attack to the Lazarus and APT38 hackers, who are raiding cryptocurrencies for the North Korean government.</p>
<h3>2. Parity Ice Age</h3>
<p>Not a new case of failure, but still worth learning from. As we know that smart contracts are eternal. Every action performed on the Ethereum blockchain requires gas as fuel. If you do it wrong then you can spend a lot of money.</p>
<p>This is the reason why blockchain developers emphasize the inclusion of a “Kill” function. However, this function does not always exist in practice. When you&#8217;re trying to build a complex multi-signature system to increase the security of Ether holders, the thing you want to hear from a newbie developer is “I accidentally killed it”.</p>
<p>The incident happened to Parity. The kill call has permanently removed the library from the blockchain thus adversely affecting the advanced parts of the platform. This security exploit has frozen more than $150 Ether in its users&#8217; wallets.</p>
<h2>Conclusion</h2>
<p>Small vulnerabilities that may be the beginning of failure and hacking may have become a big question for you, in fact, a system as sophisticated as this still has a gap to lead to losses. Even if you remember, there are so many advantages provided by smart contracts, both in terms of business people and users. Everything still needs to be fixed.</p>
<p>However, looking at the existing cases, we doubt it. How is the smart contract in the future? Do smart contracts still have a future in the business world? We have found and researched <a href="http://emveep-blog.local/blog/smart-contract-future-and-challenges/">Smart Contract Future and Challenges</a>.</p>


Can Smart Contracts Fail or Even Get Hack? Vulnerabilities & Cases

Table of Contents

Related Articles

Menu

Web Development

Mobile Development

Technologies

Have a question regarding your next project?