{"answers":{"affected":"3 open source packages ship an affected version, including vyper. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-29255 exists.","fix":"Upgrade vyper to 0.3.4 or later.","what":"CVE-2022-29255 is a high-severity vulnerability in vyperlang vyper, published on 6 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-29255 and fix it if it is affected.\n\nWhat it is: CVE-2022-29255 is a high-severity vulnerability in vyperlang vyper, published on 6 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-29255 exists.\n\nAffected packages and fixed versions:\n- vyper (PyPI): affected all versions; fixed in 0.3.4\n- vyper (PyPI): affected all versions; fixed in 0.3.4\n- vyper (PyPI): affected all versions; fixed in 0.3.4\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-29255/ (Markdown: https://insights.sbomify.com/CVE-2022-29255/index.md)","id":"CVE-2022-29255","markdown":"https://insights.sbomify.com/CVE-2022-29255/index.md","name":"CVE-2022-29255","record":{"aliases":["GHSA-4v9q-cgpw-cf38","PYSEC-2022-43053"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Vyper smart contract compiler","requires_auth":"none","summary":"Vyper compiler flaw causes double evaluation of contract addresses, leading to incorrect smart contract execution outcomes.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"vyper","vendor":"vyperlang"}],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-670","name":"Always-Incorrect Control Flow Implementation"}],"description":"Vyper is a Pythonic Smart Contract Language for the ethereum virtual machine. In versions prior to 0.3.4 when a calling an external contract with no return value, the contract address (including side effects) could be evaluated twice. This may result in incorrect outcomes for contracts. This issue has been addressed in v0.3.4.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Multiple evaluation of contract address in call in vyper","id":"CVE-2022-29255","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"business_logic","year":"2022"},"n_packages":3,"n_references":2,"next":{"headline":"Possible vulnerability at 'npm install' time in sharp if an attacker has control over build environment","id":"CVE-2022-29256"},"packages":[{"ecosystem":"PyPI","fixed":["0.3.4"],"introduced":["0"],"last_affected":[],"package":"vyper","purl":null,"source":"GHSA-4v9q-cgpw-cf38"},{"ecosystem":"PyPI","fixed":["0.3.4"],"introduced":["0"],"last_affected":[],"package":"vyper","purl":"pkg:pypi/vyper","source":"GHSA-4v9q-cgpw-cf38"},{"ecosystem":"PyPI","fixed":["0.3.4"],"introduced":["0"],"last_affected":[],"package":"vyper","purl":"pkg:pypi/vyper","source":"PYSEC-2022-43053"}],"prev":{"headline":"Failed payment recorded has completed in silverstripe/silverstripe-omnipay","id":"CVE-2022-29254"},"products":["vyper"],"published":"2022-06-06","related":[{"cvss_score":9.8,"headline":"Vyper array negative index vulnerability","id":"CVE-2024-24563","kev_date_added":null,"published":"2024-02-07"},{"cvss_score":9.8,"headline":"Vyper bounds check on built-in `slice()` function can be overflowed","id":"CVE-2024-24561","kev_date_added":null,"published":"2024-02-01"},{"cvss_score":9.1,"headline":"Vyper incorrectly allocated named re-entrancy locks","id":"CVE-2023-39363","kev_date_added":null,"published":"2023-08-07"},{"cvss_score":8.8,"headline":"Integer bounds error in Vyper","id":"CVE-2022-24845","kev_date_added":null,"published":"2022-04-13"},{"cvss_score":8.1,"headline":"Vyper vulnerable to memory corruption in certain builtins utilizing `msize`","id":"CVE-2023-42443","kev_date_added":null,"published":"2023-09-18"},{"cvss_score":7.5,"headline":"Vyper has incorrect storage layout for contracts containing large arrays","id":"CVE-2023-46247","kev_date_added":null,"published":"2023-12-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-22","vendors":["vyperlang"]},"summary":"Vyper compiler flaw causes double evaluation of contract addresses, leading to incorrect smart contract execution outcomes.","url":"https://insights.sbomify.com/CVE-2022-29255/"}