CVE-2024-24564 Vyper extract32 can ready dirty memory
Attackers can read dirty memory via the extract32 function in Vyper, potentially exposing sensitive data from smart contracts.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2024-24564?
CVE-2024-24564 is a low-severity vulnerability in vyperlang vyper, published on 26 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Vyper is a pythonic Smart Contract Language for the ethereum virtual machine. When using the built-in `extract32(b, start)`, if the `start` index provided has for side effect to update `b`, the byte array to extract `32` bytes from, it could be that some dirty memory is read and returned by `extract32`. This vulnerability is fixed in 0.4.0.
Weakness: CWE-125
Which versions are affected by CVE-2024-24564?
3 open source packages ship an affected version, including vyper. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
vyper PyPI | All versions | 0.4.0 |
vyper PyPI | All versions | 0.4.0 |
vyper PyPI | All versions | 0.4.0 |
Products include Vyperlang Vyper.
How do I fix CVE-2024-24564?
Upgrade vyper to 0.4.0 or later.
Is CVE-2024-24564 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-24564 exists.
Other vulnerabilities in vyperlang vyper
- CVE-2024-24563 Vyper array negative index vulnerability
- CVE-2024-24561 Vyper bounds check on built-in `slice()` function can be overflowed
- CVE-2023-39363 Vyper incorrectly allocated named re-entrancy locks
- CVE-2022-24845 Integer bounds error in Vyper
- CVE-2022-29255 Multiple evaluation of contract address in call in vyper
Sources
Also known as GHSA-4hwq-4cpm-8vmx, PYSEC-2024-205.