{"answers":{"affected":"3 open source packages ship an affected version, including github.com/ElrondNetwork/elrond-go. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-36061 exists.","fix":"Upgrade github.com/ElrondNetwork/elrond-go to 1.3.35 or later.","what":"CVE-2022-36061 is a medium-severity vulnerability in ElrondNetwork elrond-go, published on 6 Sep 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-36061 and fix it if it is affected.\n\nWhat it is: CVE-2022-36061 is a medium-severity vulnerability in ElrondNetwork elrond-go, published on 6 Sep 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-36061 exists.\n\nAffected packages and fixed versions:\n- github.com/ElrondNetwork/elrond-go (Go): affected all versions; fixed in 1.3.35\n- github.com/ElrondNetwork/elrond-go (Go): affected all versions; fixed in 1.3.35\n- github.com/ElrondNetwork/elrond-go (Go): affected all versions; fixed in 1.3.35\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-36061/ (Markdown: https://insights.sbomify.com/CVE-2022-36061/index.md)","id":"CVE-2022-36061","markdown":"https://insights.sbomify.com/CVE-2022-36061/index.md","name":"CVE-2022-36061","record":{"aliases":["GHSA-mv8x-668m-53fg","GO-2022-0971"],"analysis":{"component_type":"other","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Blockchain node software","requires_auth":"none","summary":"Attackers can modify smart contract state via read-only calls, bypassing intended immutability constraints in the Elrond network.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"elrond_go","vendor":"elrond"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-665","name":"Improper Initialization"}],"description":"Elrond go is the go implementation for the Elrond Network protocol. In versions prior to 1.3.35, read only calls between contracts can generate smart contracts results. For example, if contract A calls in read only mode contract B and the called function will make changes upon the contract's B state, the state will be altered for contract B as if the call was not made in the read-only mode. This can lead to some effects not designed by the original smart contracts programmers. This issue was patched in version 1.3.35. There are no known workarounds.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Elrond go can execute on same context checks in VM","id":"CVE-2022-36061","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"business_logic","year":"2022"},"n_packages":3,"n_references":3,"next":{"headline":"Grafana folders admin only permission privilege escalation","id":"CVE-2022-36062"},"packages":[{"ecosystem":"Go","fixed":["1.3.35"],"introduced":["0"],"last_affected":[],"package":"github.com/ElrondNetwork/elrond-go","purl":null,"source":"GHSA-mv8x-668m-53fg"},{"ecosystem":"Go","fixed":["1.3.35"],"introduced":["0"],"last_affected":[],"package":"github.com/ElrondNetwork/elrond-go","purl":"pkg:golang/github.com/ElrondNetwork/elrond-go","source":"GHSA-mv8x-668m-53fg"},{"ecosystem":"Go","fixed":["1.3.35"],"introduced":["0"],"last_affected":[],"package":"github.com/ElrondNetwork/elrond-go","purl":"pkg:golang/github.com/ElrondNetwork/elrond-go","source":"GO-2022-0971"}],"prev":{"headline":"Prototype pollution in matrix-react-sdk","id":"CVE-2022-36060"},"products":["elrond-go"],"published":"2022-09-06","related":[{"cvss_score":7.5,"headline":"elrond-go MultiESDTNFTTransfer call on a SC address with missing function name","id":"CVE-2022-36058","kev_date_added":null,"published":"2022-09-06"},{"cvss_score":7.2,"headline":"Elrond go Processing: fallback search of SCRs when not found in the main cache","id":"CVE-2022-46173","kev_date_added":null,"published":"2022-12-28"}],"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":"Go Vulnerability Database","prefix":"GO"},{"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":["ElrondNetwork"]},"summary":"Attackers can modify smart contract state via read-only calls, bypassing intended immutability constraints in the Elrond network.","url":"https://insights.sbomify.com/CVE-2022-36061/"}