CVE-2020-11072 json
False-negative validation results in MINT transactions with invalid baton
published 2020-05-12 6 y ago modified 2026-09-10 1 mo ago also GHSA-4w97-57v2-3w44 , EUVD-2020-0410
- cvss
- 8.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 64%
- public exploits
- 0
- none known
Summary
In SLP Validate (npm package slp-validate) before version 1.2.1, 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 has been fixed in slp-validate in version 1.2.1. Additonally, slpjs version 0.27.2 has a related fix under related CVE-2020-11071.
Patch / fix
- npm slp-validate 1.2.1
- simpleledger slp-validate 1.2.1
Exploit prediction
1.04% chance of exploitation in the next 30 days, higher than 64% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.6 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N |
| NVD | 3.1 | 8.6 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
| GitHub | 3.1 | 8.6 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | slp-validate | <1.2.1 |
1.2.1 |
Affected products
- simpleledger slp-validate
Classification
- Weakness
-
- CWE-697 Incorrect Comparison
References
-
github.com
/simpleledger/slp-validate/commit/cde95c0c6470dceb4f023cd462f904135ebd73e7
web, patch, third-party-advisory
-
github.com
/simpleledger/slp-validate/security/advisories/GHSA-4w97-57v2-3w44
web, third-party-advisory
-
github.com
/simpleledger/slp-validate.js/security/advisories/GHSA-4w97-57v2-3w44
web
-
nvd.nist.gov
/vuln/detail/CVE-2020-11072
advisory
Sources
- CVE List CVE-2020-11072
- GitHub Advisory GHSA-4w97-57v2-3w44
- NVD CVE-2020-11072
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.