CVE-2024-32645: vyper performs incorrect topic logging in raw_log

CVE-2024-32645 · Severity: low · CVSS 3.1 · Published 2024-04-25

Vyper is a pythonic Smart Contract Language for the Ethereum virtual machine. In versions 0.3.10 and prior, incorrect values can be logged when `raw_log` builtin is called with memory or storage arguments to be used as topics. A contract search was performed and no vulnerable contracts were found in production. The `build_IR` function of the `RawLog` class fails to properly unwrap the variables provided as topics. Consequently, incorrect values are logged as topics. As of time of publication, no fixed version is available.

Technologies: vyper (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2024-32645 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2024-32645 being exploited in the wild.
How severe is CVE-2024-32645?
Low severity, with a CVSS score of 3.1, published 25 April 2024.
Which products and versions are affected?
vyper (PyPI) ECOSYSTEM:introduced=0,fixed=0.4.0.
Is there a fix for CVE-2024-32645?
Yes. vyper (PyPI): upgrade to 0.4.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2024-32645?
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 or later
    pip install "vyper>=0.4.0"

Affected products

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

Identifiers

  • CVE-2024-32645
  • GHSA-xchq-w5r3-4wg3
  • PYSEC-2024-206

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