{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-46232 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-46232 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-46232 is a medium-severity vulnerability in matter-labs era-compiler-vyper, published on 25 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-46232 and fix it if it is affected.\n\nWhat it is: CVE-2023-46232 is a medium-severity vulnerability in matter-labs era-compiler-vyper, published on 25 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-46232 in the wild and no public exploit code.\n\nAffected product: matter-labs era-compiler-vyper. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2023-46232/ (Markdown: https://insights.sbomify.com/CVE-2023-46232/index.md)","id":"CVE-2023-46232","markdown":"https://insights.sbomify.com/CVE-2023-46232/index.md","name":"CVE-2023-46232","record":{"aliases":["GHSA-h8jv-969m-94r4"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Vyper compiler","requires_auth":"none","summary":"A compiler bug causes incorrect initialization of immutable variables in Vyper contracts, leading to data corruption that requires upgrading and redeploying contracts.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"zkvyper","vendor":"matter-labs"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-471","name":"Modification of Assumed-Immutable Data (MAID)"}],"description":"era-compiler-vyper is the EraVM Vyper compiler for zkSync Era, a layer 2 rollup that uses zero-knowledge proofs to scale Ethereum. Prior to era-compiler-vype version 1.3.10, a bug prevented the initialization of the first immutable variable for Vyper contracts meeting certain criteria. The problem arises when there is a String or Array with more 256-bit words allocated than initialized. It results in the second word’s index unset, that is effectively set to 0, so the first immutable value with the actual 0 index is overwritten in the ImmutableSimulator. Version 1.3.10 fixes this issue by setting all indexes in advance. The problem will go away, but it will get more expensive if the user allocates a lot of uninitialized space, e.g. `String[4096]`. Upgrading and redeploying affected contracts is the only way of working around the issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"era-compiler-vyper First Immutable Variable Initialization vulnerability","id":"CVE-2023-46232","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"crypto-js PBKDF2 1,000 times weaker than specified in 1993 and 1.3M times weaker than current standard","id":"CVE-2023-46233"},"packages":[],"prev":{"headline":"Session Token Disclosure to Internal Log Files in Splunk Add-on Builder","id":"CVE-2023-46231"},"products":["era-compiler-vyper"],"published":"2023-10-25","related":[{"cvss_score":7.5,"headline":"zkvyper ignored loop range bounds","id":"CVE-2024-43366","kev_date_added":null,"published":"2024-08-15"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-09-10","vendors":["matter-labs"]},"summary":"A compiler bug causes incorrect initialization of immutable variables in Vyper contracts, leading to data corruption that requires upgrading and redeploying contracts.","url":"https://insights.sbomify.com/CVE-2023-46232/"}