Below, you can find a JSON-formatted list of some of the known security-relevant bugs in the
Solidity compiler. The file itself is hosted in the Github repository.
The list stretches back as far as version 0.3.0, bugs known to be present only
in versions preceding that are not listed.

There is another file called 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
compiler version instead of a released version. This list does not keep
track of unreleased or nightly versions.

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:

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: very low, 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.

[{"name":"ZeroFunctionSelector","summary":"It is possible to craft the name of a function such that it is executed instead of the fallback function in very specific circumstances.","description":"If a function has a selector consisting only of zeros, is payable and part of a contract that does not have a fallback function and at most five external functions in total, this function is called instead of the fallback function if Ether is sent to the contract without data.","fixed":"0.4.18","severity":"very low"},{"name":"DelegateCallReturnValue","summary":"The low-level .delegatecall() does not return the execution outcome, but converts the value returned by the functioned called to a boolean instead.","description":"The return value of the low-level .delegatecall() function is taken from a position in memory, where the call data or the return data resides. This value is interpreted as a boolean and put onto the stack. This means if the called function returns at least 32 zero bytes, .delegatecall() returns false even if the call was successuful.","introduced":"0.3.0","fixed":"0.4.15","severity":"low"},{"name":"ECRecoverMalformedInput","summary":"The ecrecover() builtin can return garbage for malformed input.","description":"The ecrecover precompile does not properly signal failure for malformed input (especially in the 'v' argument) and thus the Solidity function can return data that was previously present in the return area in memory.","fixed":"0.4.14","severity":"medium"},{"name":"SkipEmptyStringLiteral","summary":"If \"\" is used in a function call, the following function arguments will not be correctly passed to the function.","description":"If the empty string literal \"\" is used as an argument in a function call, it is skipped by the encoder. This has the effect that the encoding of all arguments following this is shifted left by 32 bytes and thus the function call data is corrupted.","fixed":"0.4.12","severity":"low"},{"name":"ConstantOptimizerSubtraction","summary":"In some situations, the optimizer replaces certain numbers in the code with routines that compute different numbers.","description":"The optimizer tries to represent any number in the bytecode by routines that compute them with less gas. For some special numbers, an incorrect routine is generated. This could allow an attacker to e.g. trick victims about a specific amount of ether, or function calls to call different functions (or none at all).","link":"https://blog.ethereum.org/2017/05/03/solidity-optimizer-bug/","fixed":"0.4.11","severity":"low","conditions":{"optimizer":true}},{"name":"IdentityPrecompileReturnIgnored","summary":"Failure of the identity precompile was ignored.","description":"Calls to the identity contract, which is used for copying memory, ignored its return value. On the public chain, calls to the identity precompile can be made in a way that they never fail, but this might be different on private chains.","severity":"low","fixed":"0.4.7"},{"name":"OptimizerStateKnowledgeNotResetForJumpdest","summary":"The optimizer did not properly reset its internal state at jump destinations, which could lead to data corruption.","description":"The optimizer performs symbolic execution at certain stages. At jump destinations, multiple code paths join and thus it has to compute a common state from the incoming edges. Computing this common state was simplified to just use the empty state, but this implementation was not done properly. This bug can cause data corruption.","severity":"medium","introduced":"0.4.5","fixed":"0.4.6","conditions":{"optimizer":true}},{"name":"HighOrderByteCleanStorage","summary":"For short types, the high order bytes were not cleaned properly and could overwrite existing data.","description":"Types shorter than 32 bytes are packed together into the same 32 byte storage slot, but storage writes always write 32 bytes. For some types, the higher order bytes were not cleaned properly, which made it sometimes possible to overwrite a variable in storage when writing to another one.","link":"https://blog.ethereum.org/2016/11/01/security-alert-solidity-variables-can-overwritten-storage/","severity":"high","introduced":"0.1.6","fixed":"0.4.4"},{"name":"OptimizerStaleKnowledgeAboutSHA3","summary":"The optimizer did not properly reset its knowledge about SHA3 operations resulting in some hashes (also used for storage variable positions) not being calculated correctly.","description":"The optimizer performs symbolic execution in order to save re-evaluating expressions whose value is already known. This knowledge was not properly reset across control flow paths and thus the optimizer sometimes thought that the result of a SHA3 operation is already present on the stack. This could result in data corruption by accessing the wrong storage slot.","severity":"medium","fixed":"0.4.3","conditions":{"optimizer":true}},{"name":"LibrariesNotCallableFromPayableFunctions","summary":"Library functions threw an exception when called from a call that received Ether.","description":"Library functions are protected against sending them Ether through a call. Since the DELEGATECALL opcode forwards the information about how much Ether was sent with a call, the library function incorrectly assumed that Ether was sent to the library and threw an exception.","severity":"low","introduced":"0.4.0","fixed":"0.4.2"},{"name":"SendFailsForZeroEther","summary":"The send function did not provide enough gas to the recipient if no Ether was sent with it.","description":"The recipient of an Ether transfer automatically receives a certain amount of gas from the EVM to handle the transfer. In the case of a zero-transfer, this gas is not provided which causes the recipient to throw an exception.","severity":"low","fixed":"0.4.0"},{"name":"DynamicAllocationInfiniteLoop","summary":"Dynamic allocation of an empty memory array caused an infinite loop and thus an exception.","description":"Memory arrays can be created provided a length. If this length is zero, code was generated that did not terminate and thus consumed all gas.","severity":"low","fixed":"0.3.6"},{"name":"OptimizerClearStateOnCodePathJoin","summary":"The optimizer did not properly reset its internal state at jump destinations, which could lead to data corruption.","description":"The optimizer performs symbolic execution at certain stages. At jump destinations, multiple code paths join and thus it has to compute a common state from the incoming edges. Computing this common state was not done correctly. This bug can cause data corruption, but it is probably quite hard to use for targeted attacks.","severity":"low","fixed":"0.3.6","conditions":{"optimizer":true}},{"name":"CleanBytesHigherOrderBits","summary":"The higher order bits of short bytesNN types were not cleaned before comparison.","description":"Two variables of type bytesNN were considered different if their higher order bits, which are not part of the actual value, were different. An attacker might use this to reach seemingly unreachable code paths by providing incorrectly formatted input data.","severity":"medium/high","fixed":"0.3.3"},{"name":"ArrayAccessCleanHigherOrderBits","summary":"Access to array elements for arrays of types with less than 32 bytes did not correctly clean the higher order bits, causing corruption in other array elements.","description":"Multiple elements of an array of values that are shorter than 17 bytes are packed into the same storage slot. Writing to a single element of such an array did not properly clean the higher order bytes and thus could lead to data corruption.","severity":"medium/high","fixed":"0.3.1"},{"name":"AncientCompiler","summary":"This compiler version is ancient and might contain several undocumented or undiscovered bugs.","description":"The list of bugs is only kept for compiler versions starting from 0.3.0, so older versions might contain undocumented bugs.","severity":"high","fixed":"0.3.0"}]