Repository navigation
Releases
Releases · activeledger/SDK-JS
v2.7.1
Security
sdk-coreno longer allows vulnerable releases of its HTTP stack. It depended onaxios ^1.7.0, a range that lets an install with an existing lockfile stay on an axios release with known high-severity advisories, and onfollow-redirectsonly through axios. The floors are nowaxios ^1.20.0andfollow-redirects ^1.16.2(a direct dependency, so the floor holds whichever axios is picked).- axios before 1.20.0: a ReDoS in the data-URL parser that freezes the event loop, a ReDoS in proxy bypass handling reachable through an untrusted redirect
Location, redirect-based SSRF whenmaxRedirects: 0is not enforced by the fetch adapter, an HTTP/2 adapter that bypasses configured DNS lookup and proxy controls, and several prototype-pollution gadgets in request configuration. - follow-redirects 1.16.0 and 1.16.1: credential headers (
Authorizationand similar) can follow a cross-origin redirect. - What to do: upgrade
@activeledger/sdk-core(andsdk-nodeorsdk-web, which depend on it) to 2.7.1, then refresh your lockfile so it resolves axios 1.20.0 or newer and follow-redirects 1.16.2 or newer (for examplenpm update axios follow-redirects, orpnpm update axios follow-redirects -r). Installing 2.7.1 alone is not enough if your lockfile already pins the old releases. This repository's own lockfile already resolved patched releases; the change is to the range everyone else installs. - No API change.
- axios before 1.20.0: a ReDoS in the data-URL parser that freezes the event loop, a ReDoS in proxy bypass handling reachable through an untrusted redirect
Tests
- Tests fail if the declared floors are lowered or this repository's lockfile resolves a release below them.
v2.7.0
Changed
- A reply counts as committed only if it is a 2xx JSON object with a
$summaryobject.Connection.sendTransactionnow rejects a 2xx whose body is{}, an HTML proxy page or empty, andonboardKeysets an identity only when the reply is committed (a$summarywith noerrors) and contains the new stream. A ledger rejection delivered as HTTP 200 still resolves fromsendTransaction, carrying its$summary.errors. What to do: if you treated any resolvedsendTransactionas success, checkisCommitted(response)(new export) instead. - sdk-node
importKeyvalidates the key file. It checks thetype, the key encodings and lengths, and that the private and public keys belong together. A file that fails now rejects with a clear error where it used to be accepted. What to do: re-export any key file that was assembled by hand or edited. - sdk-web
fromHexrejects non-hex characters and odd lengths (an optional0xis accepted, as in sdk-node). What to do: pass valid hex.
Fixed
- sdk-web
restoreBIP39Key(..., { validate: false })rejected a non-BIP-39 phrase that sdk-node accepts, because@scure/bip39validates insidemnemonicToSeedSync. The seed is now computed with PBKDF2-HMAC-SHA512 directly, so the same phrase gives the same key on both. New exportunvalidatedSeedinrecovery. ISummaryObjecthad noerrors, so TypeScript users had to cast$summary. It now has an optionalerrors?: string[], and the cast inonboardKeyis gone.- sdk-node
verifythrew on a public key OpenSSL cannot load (for example an uncompressed point not on secp256k1). It now returnsfalse, as sdk-web does.
Performance
- sdk-node secp256k1 signing parses the private key once per signature instead of twice. Measured on Node 24.19 (500 signs per sample, WSL2): 1.12-1.25 ms to 0.78-0.79 ms per signature. Output is unchanged.
Tests and CI
- Coverage for
Connection,LedgerEvents,labelledTransactionoptions, node key file import and export, ASN.1 and the web wrappers. scripts/smoke-pack.mjs(build, pack and install the three packages into a fresh project) now runs in CI.- Live-network suite for sdk-node, skipped unless
AL_NODESandAL_STORAGEare set. scripts/verify-input-validation.mjschecks that sdk-node and sdk-web agree on input validation, and runs innpm test.- README links to the hosted documentation.
v2.6.0
v2.5.1
What's Changed
- fix(node): RSA signing broken by low-S folding; refuse ungeneratable key types by @AdmWalker in #19
Full Changelog: v2.5.0...v2.5.1
v2.5.0
v2.4.0
v2.3.0
v2.2.0
What's Changed
- fix: the GitHub release step was skipped whenever release.yml called it by @AdmWalker in #7
- test: cross-repo interop harness and post-quantum vectors by @AdmWalker in #9
- Publish secp256k1 test vectors alongside the post-quantum ones by @AdmWalker in #10
- Publish deterministic secp256k1 signatures and guard low-S coverage by @AdmWalker in #11
- Publish the high-S form of each secp256k1 signature by @AdmWalker in #12
- Correct why the high-S form is published by @AdmWalker in #13
- sdk-node emitted high-S signatures about half the time by @AdmWalker in #14
- falcon-512 keygen IS portable from a seed — the header said otherwise by @AdmWalker in #15
- feat: PayloadHandler - sign and verify things that are not transactions by @AdmWalker in #8
- feat: derive keys from a seed, and recover post-quantum keys from a phrase by @AdmWalker in #16
Full Changelog: v2.1.1...v2.2.0
v2.1.1
What's Changed
- docs: lead with post-quantum keys, and show how to choose one by @AdmWalker in #5
- ci: drop lerna, and actually create the GitHub release by @AdmWalker in #6
Full Changelog: v2.1.0...v2.1.1
v2.1.0
What's Changed
- feat: post-quantum keys in sdk-node and sdk-web by @AdmWalker in #3
- docs: changelog for 2.1.0 by @AdmWalker in #4
Full Changelog: v2.0.2...v2.1.0