{"answers":{"affected":"2 open source packages ship an affected version, including stellar-sdk. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-32738 in the wild and no public exploit code.","fix":"Upgrade stellar-sdk to 8.2.3 or later.","what":"CVE-2021-32738 is a medium-severity authentication bypass vulnerability in js-stellar-sdk, published on 2 Jul 2021. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-32738 and fix it if it is affected.\n\nWhat it is: CVE-2021-32738 is a medium-severity authentication bypass vulnerability in js-stellar-sdk, published on 2 Jul 2021. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-32738 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- stellar-sdk (npm): affected all versions; fixed in 8.2.3\n- stellar-sdk (npm): affected all versions; fixed in 8.2.3\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2021-32738/ (Markdown: https://insights.sbomify.com/CVE-2021-32738/index.md)","id":"CVE-2021-32738","markdown":"https://insights.sbomify.com/CVE-2021-32738/index.md","name":"CVE-2021-32738","record":{"aliases":["GHSA-6cgh-hjpw-q3gq"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Stellar JavaScript SDK","requires_auth":"low_privilege","summary":"The Stellar JavaScript SDK fails to verify server signatures in challenge transactions, allowing attackers to bypass authentication checks.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"js-stellar-sdk","vendor":"stellar"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"},{"id":"CWE-287","name":"Improper Authentication"}],"description":"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Utils.readChallengeTx does not verify the server account signature","id":"CVE-2021-32738","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"auth_bypass","year":"2021"},"n_packages":2,"n_references":2,"next":{"headline":"Information disclosure in icinga2","id":"CVE-2021-32739"},"packages":[{"ecosystem":"npm","fixed":["8.2.3"],"introduced":["0"],"last_affected":[],"package":"stellar-sdk","purl":null,"source":"GHSA-6cgh-hjpw-q3gq"},{"ecosystem":"npm","fixed":["8.2.3"],"introduced":["0"],"last_affected":[],"package":"stellar-sdk","purl":"pkg:npm/stellar-sdk","source":"GHSA-6cgh-hjpw-q3gq"}],"prev":{"headline":"XSS Injection in Media Collection Title was possible","id":"CVE-2021-32737"},"products":["js-stellar-sdk"],"published":"2021-07-02","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["stellar"]},"summary":"The Stellar JavaScript SDK fails to verify server signatures in challenge transactions, allowing attackers to bypass authentication checks.","url":"https://insights.sbomify.com/CVE-2021-32738/"}