{"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-15130 in the wild and no public exploit code.","fix":"Upgrade slpjs to 0.27.4 or later.","what":"CVE-2020-15130 is a high-severity vulnerability in simpleledger slpjs, published on 30 Jul 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-15130 and fix it if it is affected.\n\nWhat it is: CVE-2020-15130 is a high-severity vulnerability in simpleledger slpjs, published on 30 Jul 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-15130 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- slpjs (npm): affected all versions; fixed in 0.27.4\n- slpjs (npm): affected all versions; fixed in 0.27.4\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-15130/ (Markdown: https://insights.sbomify.com/CVE-2020-15130/index.md)","id":"CVE-2020-15130","markdown":"https://insights.sbomify.com/CVE-2020-15130/index.md","name":"CVE-2020-15130","record":{"aliases":["GHSA-cc2p-4jhr-xhhx"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"SLPJS JavaScript library","requires_auth":"none","summary":"Attackers can create invalid NFT1 child tokens without burning group tokens due to flawed validation logic in the SLPJS library.","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":7.5,"severity":"high","source":"cna","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-697","name":"Incorrect Comparison"}],"description":"In SLPJS (npm package slpjs) before version 0.27.4, there is a vulnerability to false-positive validation outcomes for the NFT1 Child Genesis transaction type. A poorly implemented SLP wallet or opportunistic attacker could create a seemingly valid NFT1 child token without burning any of the NFT1 Group token type as is required by the NFT1 specification. This is fixed in version 0.27.4.","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-positive validity for NFT1 genesis transactions in SLPJS","id":"CVE-2020-15130","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-positive validity for NFT1 genesis transactions in SLP Validate","id":"CVE-2020-15131"},"packages":[{"ecosystem":"npm","fixed":["0.27.4"],"introduced":["0"],"last_affected":[],"package":"slpjs","purl":null,"source":"GHSA-cc2p-4jhr-xhhx"},{"ecosystem":"npm","fixed":["0.27.4"],"introduced":["0"],"last_affected":[],"package":"slpjs","purl":"pkg:npm/slpjs","source":"GHSA-cc2p-4jhr-xhhx"}],"prev":{"headline":"Open redirect in Traefik","id":"CVE-2020-15129"},"products":["slpjs"],"published":"2020-07-30","related":[{"cvss_score":8.6,"headline":"False-negative validation results in MINT transactions with invalid baton","id":"CVE-2020-11071","kev_date_added":null,"published":"2020-05-12"},{"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":"Attackers can create invalid NFT1 child tokens without burning group tokens due to flawed validation logic in the SLPJS library.","url":"https://insights.sbomify.com/CVE-2020-15130/"}