CVE-2024-24561: Vyper's bounds check on built-in `slice()` function can be overflowed

CVE-2024-24561 · Severity: low · CVSS 3.1 · Published 2024-02-01

Vyper is a pythonic Smart Contract Language for the ethereum virtual machine. In versions 0.3.10 and earlier, the bounds check for slices does not account for the ability for start + length to overflow when the values aren't literals. If a slice() function uses a non-literal argument for the start or length variable, this creates the ability for an attacker to overflow the bounds check. This issue can be used to do OOB access to storage, memory or calldata addresses. It can also be used to corrupt the length slot of the respective array.

Technologies: vyper (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2024-24561 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2024-24561 being exploited in the wild.
How severe is CVE-2024-24561?
Low severity, with a CVSS score of 3.1, published 1 February 2024.
Which products and versions are affected?
vyper (PyPI) ECOSYSTEM:introduced=0,fixed=0.4.0, ECOSYSTEM:introduced=0,fixed=0.4.0b1.
Is there a fix for CVE-2024-24561?
Yes. vyper (PyPI): upgrade to 0.4.0, 0.4.0b1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2024-24561?
Check whether you run vyper (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • vyper (PyPI): upgrade to 0.4.0, 0.4.0b1 or later
    pip install "vyper>=0.4.0b1"

Affected products

  • vyper (PyPI) ECOSYSTEM:introduced=0,fixed=0.4.0, ECOSYSTEM:introduced=0,fixed=0.4.0b1

Identifiers

  • CVE-2024-24561
  • GHSA-9x7f-gwxq-6f2c
  • PYSEC-2024-149

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.