Js Stellar Sdk
Approved changes feed: RSS · Atom
cpe:2.3:a:stellar:js-stellar-sdk:*:*:*:*:*:node.js:*:*
part: a version: * update: *
| Vendor | Stellar (dff36e83-32ab-5204-bc95-0196d9a0c32c) |
|---|---|
| Product | Js Stellar Sdk (3aa48340-cb0f-510e-825e-6a47dba493e7) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | node.js |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2021-32738 |
vulnerable | 2026-06-08 05:32:07.930236 |
Utils.readChallengeTx does not verify the server account signature
MEDIUM (6.5)
js-stellar-sdk is a Javascript library for communicating with a Stellar Horizon server. The `Utils.readChallengeTx` function used in SEP-10 Stellar Web Authentication states in its function documentation that it reads and validates the challenge transaction including verifying that the `serverAccountID` has signed the transaction. In js-stellar-sdk before version 8.2.3, the function does not verify that the server has signed the transaction. Applications that also used `Utils.verifyChallengeTxThreshold` or `Utils.verifyChallengeTxSigners` to verify the signatures including the server signature on the challenge transaction are unaffected as those functions verify the server signed the transaction. Applications calling `Utils.readChallengeTx` should update to version 8.2.3, the first version with a patch for this vulnerability, to ensure that the challenge transaction is completely valid and signed by the server creating the challenge transaction.
Published: 2021-07-02T18:15:11.000Z
Updated: 2024-08-03T23:33:54.900Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.