Can not detect Bec.sol int overflow
See original GitHub issueDescribe the bug
Try ./myth -x Bec.sol
.
But no excepted report given, the only thing is the bellow.
I am not sure if I missed some options, can anyone help?
==== Exception state ====
Type: Informational
Contract: BecToken
Function name: **ambiguous** t
PC address: 5260
A reachable exception (opcode 0xfe) has been detected. This can be caused by type errors, division by zero, out-of-bounds array access, or assert violations. This is acceptable in most situations. Note however that `assert()` should only be used to check invariants. Use `require()` for regular input checking.
--------------------
In file: solidity_examples/BECToken.sol:28
assert(c >= a)
--------------------
Issue Analytics
- State:
- Created 5 years ago
- Comments:13 (5 by maintainers)
Top Results From Across the Web
BEC BatchOverflow: Could not detect the Integer Overflow in ...
Hi @vietlq . Currently, Oyente only detects overflow caused by addition. Will consider adding support for other operations like: multiplication, ...
Read more >Integer Overflow in Ethereum - Valid Network
In some cases, you can deduce that an overflow has occurred from the values that are stored after the execution of the transaction....
Read more >Detecting integer arithmetic bugs in Ethereum smart contracts
In this article, I'll show how to detect batchOverflow and similar issues in both Solidity source code and contract instances on the Ethereum ......
Read more >Ethereum Smart Contracts Vulnerabilities: Integer Overflow ...
1) BeautyChain (BEC) contract is a great example of using an integer overflow as a vulnerability to perform an attack on a contract....
Read more >SWC-101 · Overview
An overflow/underflow happens when an arithmetic operation reaches the maximum or minimum size of a type. For instance if a number is stored...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hmm, we don’t do multi-transactional analysis yet (it’s being implemented in #355) so it shouldn’t matter.
Update:
Minimal contract that cannot be solved with increased max-depth and solve timeout