Quick answers
- Is CVE-2020-11071 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2020-11071 being exploited in the wild.
- How severe is CVE-2020-11071?
- Low severity, with a CVSS score of 3.1, published 12 May 2020.
- Which products and versions are affected?
- slpjs (npm) SEMVER:introduced=0,fixed=0.27.2.
- Is there a fix for CVE-2020-11071?
- Yes. slpjs (npm): upgrade to 0.27.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2020-11071 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2020-11071?
- Check whether you run slpjs (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- slpjs (npm): upgrade to 0.27.2 or later
npm install slpjs@0.27.2
Technical details
The vulnerability is an improper input validation (CWE-697) issue in MINT transaction validation logic. The root cause is a false-negative validation check that fails to properly validate the baton field in MINT transactions, allowing invalid batons to pass validation. An attacker (or a poorly-implemented wallet) could craft a MINT transaction with an invalid baton that would be incorrectly validated as legitimate by vulnerable versions of slpjs. This could result in spending of affected tokens and destruction of the user's minting baton. The vulnerability requires no authentication or user interaction beyond wallet usage and is network-reachable to any user of the library. The fix has been patched in slpjs version 0.27.2.
Affected products
- Simple Ledger slpjs before 0.27.2
Identifiers
- CVE-2020-11071
- GHSA-jc83-cpf9-q7c6
Timeline
- 2020-05-12: disclosed
- 2020-05-12: patched: Fixed in version 0.27.2