cerc-io/solidity
16
0
Fork 0
mirror of https://github.com/ethereum/solidity synced 2023-10-03 13:03:40 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Add blog post links to the bug list

Browse Source
This commit is contained in:
Alex Beregszaszi 2019-03-26 15:03:48 +00:00
parent b85fc1a692
commit 2a2e741d39
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/bugs.json
View File

@ -3,6 +3,7 @@
"name": "ABIEncoderV2PackedStorage", "name": "ABIEncoderV2PackedStorage",
"summary": "Storage structs and arrays with types shorter than 32 bytes can cause data corruption if encoded directly from storage using the experimental ABIEncoderV2.", "summary": "Storage structs and arrays with types shorter than 32 bytes can cause data corruption if encoded directly from storage using the experimental ABIEncoderV2.",
"description": "Elements of structs and arrays that are shorter than 32 bytes are not properly decoded from storage when encoded directly (i.e. not via a memory type) using ABIEncoderV2. This can cause corruption in the values themselves but can also overwrite other parts of the encoded data.", "description": "Elements of structs and arrays that are shorter than 32 bytes are not properly decoded from storage when encoded directly (i.e. not via a memory type) using ABIEncoderV2. This can cause corruption in the values themselves but can also overwrite other parts of the encoded data.",
"link": "https://blog.ethereum.org/2019/03/26/solidity-optimizer-and-abiencoderv2-bug/",
"introduced": "0.4.19", "introduced": "0.4.19",
"fixed": "0.5.7", "fixed": "0.5.7",
"severity": "low", "severity": "low",
@ -12,8 +13,9 @@
}, },
{ {
"name": "IncorrectByteInstructionOptimization", "name": "IncorrectByteInstructionOptimization",
"summary": "The optimizer incorrectly handles byte opcodes whose second argument is 31 or a constant expression that evaluates to 31. This can result in unexpected values.", "summary": "The optimizer incorrectly handles byte opcodes whose second argument is 31 or a constant expression that evaluates to 31. This can result in unexpected values.",
"description": "The optimizer incorrectly handles byte opcodes that use the constant 31 as second argument. This can happen when performing index access on bytesNN types with a compile-time constant value (not index) of 31 or when using the byte opcode in inline assembly.", "description": "The optimizer incorrectly handles byte opcodes that use the constant 31 as second argument. This can happen when performing index access on bytesNN types with a compile-time constant value (not index) of 31 or when using the byte opcode in inline assembly.",
"link": "https://blog.ethereum.org/2019/03/26/solidity-optimizer-and-abiencoderv2-bug/",
"introduced": "0.5.5", "introduced": "0.5.5",
"fixed": "0.5.7", "fixed": "0.5.7",
"severity": "very low", "severity": "very low",
@ -25,6 +27,7 @@
"name": "DoubleShiftSizeOverflow", "name": "DoubleShiftSizeOverflow",
"summary": "Double bitwise shifts by large constants whose sum overflows 256 bits can result in unexpected values.", "summary": "Double bitwise shifts by large constants whose sum overflows 256 bits can result in unexpected values.",
"description": "Nested logical shift operations whose total shift size is 2**256 or more are incorrectly optimized. This only applies to shifts by numbers of bits that are compile-time constant expressions.", "description": "Nested logical shift operations whose total shift size is 2**256 or more are incorrectly optimized. This only applies to shifts by numbers of bits that are compile-time constant expressions.",
"link": "https://blog.ethereum.org/2019/03/26/solidity-optimizer-and-abiencoderv2-bug/",
"introduced": "0.5.5", "introduced": "0.5.5",
"fixed": "0.5.6", "fixed": "0.5.6",
"severity": "low", "severity": "low",
@ -37,6 +40,7 @@
"name": "ExpExponentCleanup", "name": "ExpExponentCleanup",
"summary": "Using the ** operator with an exponent of type shorter than 256 bits can result in unexpected values.", "summary": "Using the ** operator with an exponent of type shorter than 256 bits can result in unexpected values.",
"description": "Higher order bits in the exponent are not properly cleaned before the EXP opcode is applied if the type of the exponent expression is smaller than 256 bits and not smaller than the type of the base. In that case, the result might be larger than expected if the exponent is assumed to lie within the value range of the type. Literal numbers as exponents are unaffected as are exponents or bases of type uint256.", "description": "Higher order bits in the exponent are not properly cleaned before the EXP opcode is applied if the type of the exponent expression is smaller than 256 bits and not smaller than the type of the base. In that case, the result might be larger than expected if the exponent is assumed to lie within the value range of the type. Literal numbers as exponents are unaffected as are exponents or bases of type uint256.",
"link": "https://blog.ethereum.org/2018/09/13/solidity-bugfix-release/",
"fixed": "0.4.25", "fixed": "0.4.25",
"severity": "medium/high", "severity": "medium/high",
"check": {"regex-source": "[^/]\\*\\* *[^/0-9 ]"} "check": {"regex-source": "[^/]\\*\\* *[^/0-9 ]"}
@ -45,6 +49,7 @@
"name": "EventStructWrongData", "name": "EventStructWrongData",
"summary": "Using structs in events logged wrong data.", "summary": "Using structs in events logged wrong data.",
"description": "If a struct is used in an event, the address of the struct is logged instead of the actual data.", "description": "If a struct is used in an event, the address of the struct is logged instead of the actual data.",
"link": "https://blog.ethereum.org/2018/09/13/solidity-bugfix-release/",
"introduced": "0.4.17", "introduced": "0.4.17",
"fixed": "0.4.25", "fixed": "0.4.25",
"severity": "very low", "severity": "very low",
@ -54,6 +59,7 @@
"name": "NestedArrayFunctionCallDecoder", "name": "NestedArrayFunctionCallDecoder",
"summary": "Calling functions that return multi-dimensional fixed-size arrays can result in memory corruption.", "summary": "Calling functions that return multi-dimensional fixed-size arrays can result in memory corruption.",
"description": "If Solidity code calls a function that returns a multi-dimensional fixed-size array, array elements are incorrectly interpreted as memory pointers and thus can cause memory corruption if the return values are accessed. Calling functions with multi-dimensional fixed-size arrays is unaffected as is returning fixed-size arrays from function calls. The regular expression only checks if such functions are present, not if they are called, which is required for the contract to be affected.", "description": "If Solidity code calls a function that returns a multi-dimensional fixed-size array, array elements are incorrectly interpreted as memory pointers and thus can cause memory corruption if the return values are accessed. Calling functions with multi-dimensional fixed-size arrays is unaffected as is returning fixed-size arrays from function calls. The regular expression only checks if such functions are present, not if they are called, which is required for the contract to be affected.",
"link": "https://blog.ethereum.org/2018/09/13/solidity-bugfix-release/",
"introduced": "0.1.4", "introduced": "0.1.4",
"fixed": "0.4.22", "fixed": "0.4.22",
"severity": "medium", "severity": "medium",