CVE-2024-24567: Vyper's raw_call `value=` kwargs not disabled for static and delegate calls

CVE-2024-24567 · Severity: low · CVSS 3.1 · Published 2024-01-30

Vyper is a pythonic Smart Contract Language for the ethereum virtual machine. Vyper compiler allows passing a value in builtin raw_call even if the call is a delegatecall or a staticcall. But in the context of delegatecall and staticcall the handling of value is not possible due to the semantics of the respective opcodes, and vyper will silently ignore the value= argument. If the semantics of the EVM are unknown to the developer, he could suspect that by specifying the `value` kwarg, exactly the given amount will be sent along to the target. This vulnerability affects 0.3.10 and earlier versions.

Technologies: vyper (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2024-24567 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2024-24567 being exploited in the wild.
How severe is CVE-2024-24567?
Low severity, with a CVSS score of 3.1, published 30 January 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-24567?
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-24567?
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-24567
  • GHSA-x2c2-q32w-4w6m
  • PYSEC-2024-151

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