Skip to content

Utils.readChallengeTx does not verify the server account signature

Moderate severity GitHub Reviewed Published Jul 2, 2021 in stellar/js-stellar-sdk • Updated Jan 27, 2023

Package

npm stellar-sdk (npm)

Affected versions

< 8.2.3

Patched versions

8.2.3

Description

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. 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

@ire-and-curses ire-and-curses published to stellar/js-stellar-sdk Jul 2, 2021
Reviewed Jul 2, 2021
Published by the National Vulnerability Database Jul 2, 2021
Published to the GitHub Advisory Database Jul 2, 2021
Last updated Jan 27, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

EPSS score

0.050%
(20th percentile)

Weaknesses

CVE ID

CVE-2021-32738

GHSA ID

GHSA-6cgh-hjpw-q3gq

Source code

No known source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.