CVE-2024-24564Public exploitNetwork attack vector

Information disclosure via stale extract32 length

Published Feb 26, 2024 · Updated Oct 25, 2024

Out-of-bounds reads in Vyper before 0.4.0 allow remote attackers to obtain stale EVM memory from affected smart contracts. Extract32.build_IR caches the byte-array pointer and length before evaluating start, but not the contents, so a side effect that changes the array pairs an obsolete length with new data. A deployed contract must pass a start expression that mutates the same array; extract32 then returns dirty bytes instead of the intended value.

CVSS severity3.7
Low
EPSS probability0.56%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Out-of-bounds reads in Vyper before 0.4.0 allow remote attackers to obtain stale EVM memory from affected smart contracts. Extract32.build_IR caches the byte-array pointer and length before evaluating start, but not the contents, so a side effect that changes the array pairs an obsolete length with new data. A deployed contract must pass a start expression that mutates the same array; extract32 then returns dirty bytes instead of the intended value.

The record

CVE
CVE-2024-24564
Published
Feb 26, 2024
Updated
Oct 25, 2024
Vendor
Vyper
Product
Vyper
Classifications
CWE-125
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Feb 26, 2024CVE publishedPublication date reported by the CVE source.
  2. Oct 25, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <0.4.0
  2. Affected versionversion=< 0.4.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Vyper · Vyperversion=0 <0.4.0; version=< 0.4.0

Published CVSS scores

3.7GitHub, Inc.CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
5.3NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-125Out-of-bounds Read

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo