2017-04-12 10:23:34 +00:00
|
|
|
.. index:: Bugs
|
|
|
|
|
|
|
|
|
|
.. _known_bugs:
|
|
|
|
|
|
|
|
|
|
##################
|
|
|
|
|
List of Known Bugs
|
|
|
|
|
##################
|
|
|
|
|
|
2017-04-18 09:40:00 +00:00
|
|
|
Below, you can find a JSON-formatted list of some of the known security-relevant bugs in the
|
2017-04-12 10:23:34 +00:00
|
|
|
Solidity compiler. The file itself is hosted in the `Github repository
|
|
|
|
|
<https://github.com/ethereum/solidity/blob/develop/docs/bugs.json>`_.
|
|
|
|
|
The list stretches back as far as version 0.3.0, bugs known to be present only
|
2017-04-12 13:35:25 +00:00
|
|
|
in versions preceding that are not listed.
|
|
|
|
|
|
|
|
|
|
There is another file called `bugs_by_version.json
|
|
|
|
|
<https://github.com/ethereum/solidity/blob/develop/docs/bugs_by_version.json>`_,
|
|
|
|
|
which can be used to check which bugs affect a specific version of the compiler.
|
|
|
|
|
|
|
|
|
|
Contract source verification tools and also other tools interacting with
|
|
|
|
|
contracts should consult this list according to the following criteria:
|
|
|
|
|
|
|
|
|
|
- It is mildly suspicious if a contract was compiled with a nightly
|
2017-04-18 10:20:39 +00:00
|
|
|
compiler version instead of a released version. This list does not keep
|
|
|
|
|
track of unreleased or nightly versions.
|
2017-04-12 13:35:25 +00:00
|
|
|
- It is also mildly suspicious if a contract was compiled with a version that was
|
|
|
|
|
not the most recent at the time the contract was created. For contracts
|
|
|
|
|
created from other contracts, you have to follow the creation chain
|
|
|
|
|
back to a transaction and use the date of that transaction as creation date.
|
|
|
|
|
- It is highly suspicious if a contract was compiled with a compiler that
|
|
|
|
|
contains a known bug and the contract was created at a time where a newer
|
|
|
|
|
compiler version containing a fix was already released.
|
|
|
|
|
|
|
|
|
|
The JSON file of known bugs below is an array of objects, one for each bug,
|
|
|
|
|
with the following keys:
|
2017-04-12 10:23:34 +00:00
|
|
|
|
|
|
|
|
name
|
|
|
|
|
Unique name given to the bug
|
|
|
|
|
summary
|
|
|
|
|
Short description of the bug
|
|
|
|
|
description
|
|
|
|
|
Detailed description of the bug
|
|
|
|
|
link
|
|
|
|
|
URL of a website with more detailed information, optional
|
|
|
|
|
introduced
|
|
|
|
|
The first published compiler version that contained the bug, optional
|
|
|
|
|
fixed
|
|
|
|
|
The first published compiler version that did not contain the bug anymore
|
|
|
|
|
publish
|
|
|
|
|
The date at which the bug became known publicly, optional
|
|
|
|
|
severity
|
|
|
|
|
Severity of the bug: low, medium, high. Takes into account
|
|
|
|
|
discoverability in contract tests, likelihood of occurrence and
|
|
|
|
|
potential damage by exploits.
|
|
|
|
|
conditions
|
|
|
|
|
Conditions that have to be met to trigger the bug. Currently, this
|
|
|
|
|
is an object that can contain a boolean value ``optimizer``, which
|
|
|
|
|
means that the optimizer has to be switched on to enable the bug.
|
|
|
|
|
If no conditions are given, assume that the bug is present.
|
|
|
|
|
|
|
|
|
|
.. literalinclude:: bugs.json
|
|
|
|
|
:language: js
|
