Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

GHSA-jc83-cpf9-q7c6

HIGHFix: simpleledger/slpjs@3671be2

GHSA-jc83-cpf9-q7c6 is a high-severity (CVSS 8.6) CWE-697 vulnerability in slpjs. O3 Security confirms whether GHSA-jc83-cpf9-q7c6 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

False-negative validation results in MINT transactions with invalid baton

Also known asCVE-2020-11071
Published
May 12, 2020
Updated
Jul 8, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Jul 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

9other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
slpjsnpm
316downloads / week

Description

Impact

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.

Patches

npm package slpjs has been patched and published as version 0.27.2.

Workarounds

Upgrade to slpjs 0.27.2.

References

For more information

If you have any questions or comments about this advisory:

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmslpjsall versions0.27.2

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for slpjs. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update slpjs to 0.27.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jc83-cpf9-q7c6 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-jc83-cpf9-q7c6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-jc83-cpf9-q7c6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Users could experience false-negative validation outcomes for [MINT](https://github.com/simpleledger/slp-specifications/blob/master/slp-token-type-1.md#mint---extended-minting-transaction) 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. ### Patches npm package [slpjs](https://www.npmjs.com/package/slpjs) has been patched and published as version 0.27.2. ### Workarounds Upgrade to slpjs 0.27.2. ### References * slpjs [commit](https://github.com/simpleledger/slpjs/
O3 Security · Impact-Aware SCA

Is GHSA-jc83-cpf9-q7c6 in your dependencies?

O3 detects GHSA-jc83-cpf9-q7c6 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-jc83-cpf9-q7c6: slpjs (High 8.6) | O3 Security