{"answers":{"affected":"3 open source packages ship an affected version, including github.com/multiversx/mx-chain-go. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-34458 in the wild and no public exploit code.","fix":"Upgrade github.com/multiversx/mx-chain-go to 1.4.17 or later.","what":"CVE-2023-34458 is a high-severity denial of service vulnerability in multiversx mx-chain-go, published on 13 Jul 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-34458 and fix it if it is affected.\n\nWhat it is: CVE-2023-34458 is a high-severity denial of service vulnerability in multiversx mx-chain-go, published on 13 Jul 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-34458 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/multiversx/mx-chain-go (Go): affected all versions; fixed in 1.4.17\n- github.com/multiversx/mx-chain-go (Go): affected all versions; fixed in 1.4.17\n- github.com/multiversx/mx-chain-go (Go): affected all versions; fixed in 1.4.17\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-34458/ (Markdown: https://insights.sbomify.com/CVE-2023-34458/index.md)","id":"CVE-2023-34458","markdown":"https://insights.sbomify.com/CVE-2023-34458/index.md","name":"CVE-2023-34458","record":{"aliases":["GHSA-j494-7x2v-vvvp","GO-2023-1912"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"MultiversX blockchain node","requires_auth":"low_privilege","summary":"Attackers can cause a limited denial of service on targeted accounts by exploiting a nonce increment bug in relayed transactions.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"mx-chain-go","vendor":"multiversx"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:H","version":"3.1"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"mx-chain-go is the official implementation of the MultiversX blockchain protocol, written in golang. When executing a relayed transaction, if the inner transaction failed, it would have increased the inner transaction's sender account nonce. This could have contributed to a limited DoS attack on a targeted account. The fix is a breaking change so a new flag `RelayedNonceFixEnableEpoch` was needed. This was a strict processing issue while validating blocks on a chain. This vulnerability has been patched in version 1.4.17.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"mx-chain-go's relayed transactions always increment nonce","id":"CVE-2023-34458","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"denial_of_service","year":"2023"},"n_packages":3,"n_references":4,"next":{"headline":"OpenZeppelin Contracts's MerkleProof multiproofs may allow proving arbitrary leaves for specific trees","id":"CVE-2023-34459"},"packages":[{"ecosystem":"Go","fixed":["1.4.17"],"introduced":["0"],"last_affected":[],"package":"github.com/multiversx/mx-chain-go","purl":null,"source":"GHSA-j494-7x2v-vvvp"},{"ecosystem":"Go","fixed":["1.4.17"],"introduced":["0"],"last_affected":[],"package":"github.com/multiversx/mx-chain-go","purl":"pkg:golang/github.com/multiversx/mx-chain-go","source":"GHSA-j494-7x2v-vvvp"},{"ecosystem":"Go","fixed":["1.4.17"],"introduced":["0"],"last_affected":[],"package":"github.com/multiversx/mx-chain-go","purl":"pkg:golang/github.com/multiversx/mx-chain-go","source":"GO-2023-1912"}],"prev":{"headline":"MechanicalSoup vulnerable to malicious web server reading arbitrary files on client using file input inside HTML form","id":"CVE-2023-34457"},"products":["mx-chain-go"],"published":"2023-07-13","related":[{"cvss_score":8.6,"headline":"mx-chain-go does not treat invalid transaction with wrong username correctly","id":"CVE-2023-33964","kev_date_added":null,"published":"2023-05-31"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-10-22","vendors":["multiversx"]},"summary":"Attackers can cause a limited denial of service on targeted accounts by exploiting a nonce increment bug in relayed transactions.","url":"https://insights.sbomify.com/CVE-2023-34458/"}