https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 23:30:11 +0000 https://cve.radiocsirt.org/vuln/cve-2023-30629 <p><strong>Affected:</strong> vyperlang vyper</p> <p>Vyper is a Pythonic Smart Contract Language for the ethereum virtual machine. In versions 0.3.1 through 0.3.7, the Vyper compiler generates the wrong bytecode. Any contract that uses the `raw_call` with `revert_on_failure=False` and `max_outsize=0` receives the wrong response from `raw_call`. Depending on the memory garbage, the result can be either `True` or `False`. A patch is available and, as of time of publication, anticipated to be part of Vyper 0.3.8. As a workaround, one may always put `max_outsize&gt;0`.</p> <p><strong>Affected:</strong> vyperlang vyper</p> <p>Vyper is a Pythonic Smart Contract Language for the ethereum virtual machine. In versions 0.3.1 through 0.3.7, the Vyper compiler generates the wrong bytecode. Any contract that uses the `raw_call` with `revert_on_failure=False` and `max_outsize=0` receives the wrong response from `raw_call`. Depending on the memory garbage, the result can be either `True` or `False`. A patch is available and, as of time of publication, anticipated to be part of Vyper 0.3.8. As a workaround, one may always put `max_outsize&gt;0`.</p> https://cve.radiocsirt.org/vuln/cve-2023-30629 https://cve.radiocsirt.org/vuln/ghsa-w9g2-3w7p-72g9 <p><strong>Affected:</strong> PyPI: vyper</p> <p>### Background During the audit of [Lido&#39;s Gate Seals](https://github.com/lidofinance/gate-seals) code [statemind](https://statemind.io) team identified a weird behavior of the code that uses `raw_call`: https://github.com/lidofinance/gate-seals/blob/051593e74df01a4131c485b4fda52e691cd4b7d8/contracts/GateSeal.vy#L164 .</p> <p>Construction like this: ```vyper success = raw_call( sealable, _abi_encode(SEAL_DURATION_SECONDS, method_id=method_id(&#34;pauseFor(uint256)&#34;)), revert_on_failure=False ) ``` was not fully documented: https://docs.vyperlang.org/en/v0.3.7/built-in-functions.html#raw_call .</p> <p>The documentation says that: if `max_outsize=0` it should return nothing and then it says that if `revert_on_failure=False` it should return a `success` flag in the tuple of response, but what if `max_outsize=0` and `revert_on_failure=False`.</p> <p>&lt;img width=&#34;715&#34; alt=&#34;image&#34; src=&#34;https://user-images.githubusercontent.com/22330612/232125364-d2b3bbac-0b4f-40cb-80ff-f55d8eafef44.png&#34;&gt;</p> <p>So the team started researching what exactly happened in that case, after some research we found that the Vyper compiler generates the wrong bytecode in that case, it generates the sequence: ``` CALL // call MLOAD // MLOAD is wrong since the CALL result is already stored in the stack ```</p> <p>### Impact Example of buggy code: ```vyper @external def returnSome(calling: address, a: uint256) -&gt; bool: success: bool = false success = raw_call( calling, _abi_encode(a, method_id=method_id(&#34;a(…</p> <p><strong>Affected:</strong> PyPI: vyper</p> <p>### Background During the audit of [Lido&#39;s Gate Seals](https://github.com/lidofinance/gate-seals) code [statemind](https://statemind.io) team identified a weird behavior of the code that uses `raw_call`: https://github.com/lidofinance/gate-seals/blob/051593e74df01a4131c485b4fda52e691cd4b7d8/contracts/GateSeal.vy#L164 .</p> <p>Construction like this: ```vyper success = raw_call( sealable, _abi_encode(SEAL_DURATION_SECONDS, method_id=method_id(&#34;pauseFor(uint256)&#34;)), revert_on_failure=False ) ``` was not fully documented: https://docs.vyperlang.org/en/v0.3.7/built-in-functions.html#raw_call .</p> <p>The documentation says that: if `max_outsize=0` it should return nothing and then it says that if `revert_on_failure=False` it should return a `success` flag in the tuple of response, but what if `max_outsize=0` and `revert_on_failure=False`.</p> <p>&lt;img width=&#34;715&#34; alt=&#34;image&#34; src=&#34;https://user-images.githubusercontent.com/22330612/232125364-d2b3bbac-0b4f-40cb-80ff-f55d8eafef44.png&#34;&gt;</p> <p>So the team started researching what exactly happened in that case, after some research we found that the Vyper compiler generates the wrong bytecode in that case, it generates the sequence: ``` CALL // call MLOAD // MLOAD is wrong since the CALL result is already stored in the stack ```</p> <p>### Impact Example of buggy code: ```vyper @external def returnSome(calling: address, a: uint256) -&gt; bool: success: bool = false success = raw_call( calling, _abi_encode(a, method_id=method_id(&#34;a(…</p> https://cve.radiocsirt.org/vuln/ghsa-w9g2-3w7p-72g9