{"answers":{"affected":"2 open source packages ship an affected version, including snarkjs. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-33252 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-33252 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-33252 is a high-severity vulnerability in n/a, published on 21 May 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-33252 and fix it if it is affected.\n\nWhat it is: CVE-2023-33252 is a high-severity vulnerability in n/a, published on 21 May 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-33252 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- snarkjs (npm): affected all versions up to 0.6.11; no fix listed\n- snarkjs (npm): affected all versions up to 0.6.11; no fix listed\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-33252/ (Markdown: https://insights.sbomify.com/CVE-2023-33252/index.md)","id":"CVE-2023-33252","markdown":"https://insights.sbomify.com/CVE-2023-33252/index.md","name":"CVE-2023-33252","record":{"aliases":["GHSA-xp5g-jhg3-3rg2"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"snarkjs JavaScript library","requires_auth":"none","summary":"Attackers can perform double spending in snarkjs due to missing validation of publicSignals length against the field modulus.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"snarkjs","vendor":"0kims"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"iden3 snarkjs through 0.6.11 allows double spending because there is no validation that the publicSignals length is less than the field modulus.","ecosystems":["npm"],"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":"Double spend in snarkjs","id":"CVE-2023-33252","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"business_logic","year":"2023"},"n_packages":2,"n_references":2,"next":{"headline":"File upload in n/a","id":"CVE-2023-33253"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.6.11"],"package":"snarkjs","purl":null,"source":"GHSA-xp5g-jhg3-3rg2"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.6.11"],"package":"snarkjs","purl":"pkg:npm/snarkjs","source":"GHSA-xp5g-jhg3-3rg2"}],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2023-33251"},"products":["n/a"],"published":"2023-05-21","related":[],"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":"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":"2025-01-21","vendors":["n/a"]},"summary":"Attackers can perform double spending in snarkjs due to missing validation of publicSignals length against the field modulus.","url":"https://insights.sbomify.com/CVE-2023-33252/"}