Forged SEP-10 challenge acceptance via omitted signature check
Published Jul 2, 2021 · Updated Aug 3, 2024
Improper signature verification in Stellar JS SDK before 8.2.3 allows remote authenticated users to have forged SEP-10 challenges accepted. Utils.readChallengeTx returns a parsed challenge without verifying that serverAccountID signed it; the patch adds verifyTxSignedBy before return. Exposure requires an application to rely on readChallengeTx without either supplemental verifier, allowing an unsigned challenge to be treated as server-issued.
Summary
What happened
Improper signature verification in Stellar JS SDK before 8.2.3 allows remote authenticated users to have forged SEP-10 challenges accepted. Utils.readChallengeTx returns a parsed challenge without verifying that serverAccountID signed it; the patch adds verifyTxSignedBy before return. Exposure requires an application to rely on readChallengeTx without either supplemental verifier, allowing an unsigned challenge to be treated as server-issued.
The record
- CVE
- CVE-2021-32738
- Published
- Jul 2, 2021
- Updated
- Aug 3, 2024
- Vendor
- Stellar Development Foundation
- Product
- Stellar JS SDK
- Classifications
- CWE-347, CWE-287
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 2, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 8.2.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo