CVE-2024-24567Public exploitNetwork attack vector

Omitted Ether transfers via ignored raw_call value

Published Jan 30, 2024 · Updated Jun 16, 2025

Improper input validation in Vyper 0.3.10 and earlier allows attackers to compile contracts that silently omit intended Ether transfers. The RawCall.build_IR method accepts a nonzero value argument with delegatecall or staticcall, although those EVM opcodes cannot transfer value and the compiler discards it. The flaw is reached only when contract source combines raw_call value= with is_delegate_call or is_static_call, producing bytecode whose payment behavior differs from the source and potentially disrupts contract accounting.

CVSS severity4.8
Medium
EPSS probability0.48%
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

Improper input validation in Vyper 0.3.10 and earlier allows attackers to compile contracts that silently omit intended Ether transfers. The RawCall.build_IR method accepts a nonzero value argument with delegatecall or staticcall, although those EVM opcodes cannot transfer value and the compiler discards it. The flaw is reached only when contract source combines raw_call value= with is_delegate_call or is_static_call, producing bytecode whose payment behavior differs from the source and potentially disrupts contract accounting.

The record

CVE
CVE-2024-24567
Published
Jan 30, 2024
Updated
Jun 16, 2025
Vendor
Vyper
Product
Vyper
Classifications
CWE-754
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jan 30, 2024CVE publishedPublication date reported by the CVE source.
  2. Jun 16, 2025Record 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.3.10

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Vyper · Vyperversion=<= 0.3.10

Published CVSS scores

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

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-754Improper Check for Unusual or Exceptional Conditions

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