{"id":"CVE-2024-24567","aliases":["GHSA-x2c2-q32w-4w6m","PYSEC-2024-151"],"title":"Vyper's raw_call `value=` kwargs not disabled for static and delegate calls","summary":"Vyper's raw_call `value=` kwargs not disabled for static and delegate calls","severity":"medium","cvss":4.8,"cvssVector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L","vendor":"vyper","product":"vyper","ecosystem":"pip","affected":["vyper < 0.4.0"],"patched":["vyper 0.4.0"],"published":"2024-01-30","updated":"2026-09-10","sourceUpdated":"2026-09-10T03:50:09.737044532Z","source":"OSV","sourceUrl":"https://osv.dev/vulnerability/GHSA-x2c2-q32w-4w6m","references":[{"url":"https://github.com/vyperlang/vyper/security/advisories/GHSA-x2c2-q32w-4w6m"},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-24567"},{"url":"https://github.com/vyperlang/vyper/pull/3755"},{"url":"https://github.com/vyperlang/vyper/commit/a2df08888c318713742c57f71465f32a1c27ed72"},{"url":"https://github.com/pypa/advisory-database/tree/main/vulns/vyper/PYSEC-2024-151.yaml"},{"url":"https://github.com/vyperlang/vyper"},{"url":"https://github.com/vyperlang/vyper/blob/9136169468f317a53b4e7448389aa315f90b95ba/vyper/builtins/functions.py#L1100"}],"tags":["osv","pip"],"epss":0.00485,"epssPercentile":0.40849,"ingestedAt":"2026-09-12T03:13:01.738Z","slug":"CVE-2024-24567","body":"## Overview\n\n### Summary\nVyper 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.\n\nA contract search was performed and no vulnerable contracts were found in production.\n\n### Details\nThe IR for `raw_call` is built in the `RawCall` class:\nhttps://github.com/vyperlang/vyper/blob/9136169468f317a53b4e7448389aa315f90b95ba/vyper/builtins/functions.py#L1100\n\nHowever, the compiler doesn't validate that if either `delegatecall` or `staticall` are provided as kwargs, that `value` wasn't set. For example, the following compiles without errors:\n```python\nraw_call(self, call_data2, max_outsize=255, is_delegate_call=True, value=msg.value/2)\n```\n\n### Impact\nIf 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. However in fact, no `value` will be sent.\n\nHere is an example of an potentially problematic implementation of multicall utilizing the `raw_call` built-in:\n```python\nvalue_accumulator: uint256 = empty(uint256)\n    results: DynArray[Result, max_value(uint8)] = []\n    return_data: Bytes[max_value(uint8)] = b\"\"\n    success: bool = empty(bool)\n    for batch in data:\n        msg_value: uint256 = batch.value\n        value_accumulator = unsafe_add(value_accumulator, msg_value)\n        if (batch.allow_failure == False):\n            return_data = raw_call(self, batch.call_data, max_outsize=255, value=msg_value, is_delegate_call=True)\n            success = True\n            results.append(Result({success: success, return_data: return_data}))\n        else:\n            success, return_data = \\\n                raw_call(self, batch.call_data, max_outsize=255, value=msg_value, is_delegate_call=True, revert_on_failure=False)\n            results.append(Result({success: success, return_data: return_data}))\n    assert msg.value == value_accumulator, \"Multicall: value mismatch\"\n    return results\n```\n\n### Patches\nFixed in https://github.com/vyperlang/vyper/pull/3755\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\n### References\n_Are there any links users can visit to find out more?_\n\n\n## Affected packages\n\n- `vyper < 0.4.0`\n\n## Remediation\n\nUpgrade to a patched release:\n\n- `vyper 0.4.0`","depth":"sunlit","depthScore":26,"depthScoreParts":{"impact":26.4,"likelihood":0.1,"exploitation":0,"ransomware":0},"changes":[]}