Bug 2366631 (CVE-2025-47774) - CVE-2025-47774 vyper: Vyper: Slice Length Zero Side-Effect Elision
Summary: CVE-2025-47774 vyper: Vyper: Slice Length Zero Side-Effect Elision
Keywords:
Status: NEW
Alias: CVE-2025-47774
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2366718 2366719
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-05-15 18:01 UTC by OSIDB Bzimport
Modified: 2025-05-16 17:34 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-05-15 18:01:21 UTC
Vyper is the Pythonic Programming Language for the Ethereum Virtual Machine. In versions up to and including 0.4.2rc1, the `slice()` builtin can elide side effects when the output length is 0, and the source bytestring is a builtin (`msg.data` or `<address>.code`). The reason is that for these source locations, the check that `length >= 1` is skipped. The result is that a 0-length bytestring constructed with slice can be passed to `make_byte_array_copier`, which elides evaluation of its source argument when the max length is 0. The impact is that side effects in the `start` argument may be elided when the `length` argument is 0, e.g. `slice(msg.data, self.do_side_effect(), 0)`. The fix in pull request 4645 disallows any invocation of `slice()` with length 0, including for the ad hoc locations discussed in this advisory. The fix is expected to be part of version 0.4.2.


Note You need to log in before you can comment on or make changes to this bug.