~ / search / GHSA-6cgh-hjpw-q3gq

GHSA-6cgh-hjpw-q3gq

Utils.readChallengeTx does not verify the server account signature

Source: GitHub Advisory Database (reviewed) Moderate CVE-2021-32738

Packages

EcosystemPackageAffectedFixed in
npm stellar-sdk < 8.2.3 8.2.3

Details

As written in the advisory (Markdown source, shown as plain text).

The `Utils.readChallengeTx` function used in [SEP-10 Stellar Web Authentication](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md) states in its function documentation that it reads and validates the challenge transaction including verifying that the `serverAccountID` has signed the transaction. The function does not verify that the server has signed the transaction and has been fixed so that it does in v8.2.3. 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 v8.2.3 to ensure that the challenge transaction is completely valid and signed by the server creating the challenge transaction.

References

External links from the advisory. They lead to third-party sites.