{"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-2024-24559 exists.","fix":"Upgrade vyper to a fixed version for your release line: 0.4.0 or 0.4.0b1.","what":"CVE-2024-24559 is a low-severity vulnerability in vyperlang vyper, published on 5 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-24559 and fix it if it is affected.\n\nWhat it is: CVE-2024-24559 is a low-severity vulnerability in vyperlang vyper, published on 5 Feb 2024. 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-2024-24559 exists.\n\nAffected packages and fixed versions:\n- vyper (PyPI): affected all versions; fixed in 0.4.0\n- vyper (PyPI): affected all versions; fixed in 0.4.0\n- vyper (PyPI): affected all versions; fixed in 0.4.0b1\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-2024-24559/ (Markdown: https://insights.sbomify.com/CVE-2024-24559/index.md)","id":"CVE-2024-24559","markdown":"https://insights.sbomify.com/CVE-2024-24559/index.md","name":"CVE-2024-24559","record":{"aliases":["GHSA-6845-xw22-ffxv","PYSEC-2024-147"],"analysis":{"component_type":"developer_tool","fix_type":"no_fix_stated","impacts":["other"],"network_reachable":"yes","non_default_config":true,"product_category":"Vyper compiler","requires_auth":"none","summary":"A stack management error in Vyper's SHA3 code generation affects manually written IR, but is not triggerable via normal compilation.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"vyper","vendor":"vyperlang"}],"cvss":{"score":3.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"}],"description":"Vyper is a Pythonic Smart Contract Language for the EVM. There is an error in the stack management when compiling the `IR` for `sha3_64`. Concretely, the `height` variable is miscalculated. The vulnerability can't be triggered without writing the `IR` by hand (that is, it cannot be triggered from regular vyper code). `sha3_64` is used for retrieval in mappings. No flow that would cache the `key` was found so the issue shouldn't be possible to trigger when compiling the compiler-generated `IR`. This issue isn't triggered during normal compilation of vyper code so the impact is low. At the time of publication there is no patch available.","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":"Vyper SHA3 code generation bug","id":"CVE-2024-24559","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"other","year":"2024"},"n_packages":3,"n_references":2,"next":{"headline":"Vyper external calls can overflow return data to return input buffer","id":"CVE-2024-24560"},"packages":[{"ecosystem":"PyPI","fixed":["0.4.0"],"introduced":["0"],"last_affected":[],"package":"vyper","purl":null,"source":"GHSA-6845-xw22-ffxv"},{"ecosystem":"PyPI","fixed":["0.4.0"],"introduced":["0"],"last_affected":[],"package":"vyper","purl":"pkg:pypi/vyper","source":"GHSA-6845-xw22-ffxv"},{"ecosystem":"PyPI","fixed":["0.4.0b1"],"introduced":["0"],"last_affected":[],"package":"vyper","purl":"pkg:pypi/vyper","source":"PYSEC-2024-147"}],"prev":{"headline":"react-query-streamed-hydration xss","id":"CVE-2024-24558"},"products":["vyper"],"published":"2024-02-05","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.2,"headline":"Multiple evaluation of contract address in call in vyper","id":"CVE-2022-29255","kev_date_added":null,"published":"2022-06-06"},{"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-26","vendors":["vyperlang"]},"summary":"A stack management error in Vyper's SHA3 code generation affects manually written IR, but is not triggerable via normal compilation.","url":"https://insights.sbomify.com/CVE-2024-24559/"}