click below
click below
Normal Size Small Size show me how
Solidity Bugs
Solidity vulnerabilities and definitions
Term | Definition |
---|---|
Race Conditions | Race conditions occur when multiple transactions are executed concurrently, leading to unpredictable results. |
Integer Overflow/Underflow | Occur when an integer value exceeds its maximum or minimum limit, leading to unexpected behavior. |
Re-Entrancy | Occurs when a contract calls back into its own code, leading to unexpected behavior and potential loss of funds. |
Denial of Service (DoS): | A vulnerability caused by the lack of proper safeguards, allowing malicious actors to deny service to legitimate users. |
Unchecked-Send | This vulnerability occurs when a contract doesn't check if the amount sent is enough to cover the transaction fee. As a result, the transaction fails, and the user loses their funds. |
Timestamp Dependence: | Occurs when a contract relies on a timestamp as part of its logic. The timestamp can be manipulated by malicious actors, resulting in unexpected behavior. |
Denial of Service (DoS) | Occurs when a contract is programmed to perform too many computations, resulting in resources being “eaten up” and the contract becoming unresponsive. |
Transaction-Ordering Dependence (TOD) | Occurs when a contract depends on the order in which transactions are processed. An attacker can manipulate the order of transactions, resulting in unexpected behavior. |
Unrestricted Access | Occurs when a contract does not restrict access to certain operations, allowing attackers to execute certain functions that should not be available to them. |
Cross-Function Race Condition: | Occurs when multiple functions of a contract are processed concurrently. This can result in the data stored in the contract being manipulated or corrupted. |
Gas Limit Attack | Occurs when an attacker sends a transaction with a higher gas limit than the contract can handle. As a result, the contract runs out of gas, resulting in unexpected behavior. |