{"answers":{"affected":"2 open source packages ship an affected version, including slpjs. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-11071 in the wild and no public exploit code.","fix":"Upgrade slpjs to 0.27.2 or later.","what":"CVE-2020-11071 is a high-severity vulnerability in simpleledger slpjs, published on 12 May 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-11071 and fix it if it is affected.\n\nWhat it is: CVE-2020-11071 is a high-severity vulnerability in simpleledger slpjs, published on 12 May 2020. 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-2020-11071 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- slpjs (npm): affected all versions; fixed in 0.27.2\n- slpjs (npm): affected all versions; fixed in 0.27.2\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-2020-11071/ (Markdown: https://insights.sbomify.com/CVE-2020-11071/index.md)","id":"CVE-2020-11071","markdown":"https://insights.sbomify.com/CVE-2020-11071/index.md","name":"CVE-2020-11071","record":{"aliases":["GHSA-jc83-cpf9-q7c6"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"SLP JavaScript library","requires_auth":"none","summary":"A logic flaw in SLPJS allows false-negative validation of MINT transactions, potentially leading to the destruction of a user's minting baton.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"slpjs","vendor":"simpleledger"}],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-697","name":"Incorrect Comparison"}],"description":"SLPJS (npm package slpjs) before version 0.27.2, has a vulnerability where users could experience false-negative validation outcomes for MINT transaction operations. A poorly implemented SLP wallet could allow spending of the affected tokens which would result in the destruction of a user's minting baton. This is fixed in version 0.27.2.","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":true,"headline":"False-negative validation results in MINT transactions with invalid baton","id":"CVE-2020-11071","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"business_logic","year":"2020"},"n_packages":2,"n_references":2,"next":{"headline":"False-negative validation results in MINT transactions with invalid baton","id":"CVE-2020-11072"},"packages":[{"ecosystem":"npm","fixed":["0.27.2"],"introduced":["0"],"last_affected":[],"package":"slpjs","purl":null,"source":"GHSA-jc83-cpf9-q7c6"},{"ecosystem":"npm","fixed":["0.27.2"],"introduced":["0"],"last_affected":[],"package":"slpjs","purl":"pkg:npm/slpjs","source":"GHSA-jc83-cpf9-q7c6"}],"prev":{"headline":"Cross-Site Scripting in SVG Sanitizer","id":"CVE-2020-11070"},"products":["slpjs"],"published":"2020-05-12","related":[{"cvss_score":7.5,"headline":"False-positive validity for NFT1 genesis transactions in SLPJS","id":"CVE-2020-15130","kev_date_added":null,"published":"2020-07-30"},{"cvss_score":5.7,"headline":"Validator parsing discrepancy due to string encoding in NPM slpjs","id":"CVE-2019-16762","kev_date_added":null,"published":"2019-11-15"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["simpleledger"]},"summary":"A logic flaw in SLPJS allows false-negative validation of MINT transactions, potentially leading to the destruction of a user's minting baton.","url":"https://insights.sbomify.com/CVE-2020-11071/"}