{"answers":{"affected":"2 open source packages ship an affected version, including @solana/pay. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-35917 in the wild and no public exploit code.","fix":"Upgrade @solana/pay to 0.2.1 or later.","what":"CVE-2022-35917 is a medium-severity vulnerability in solana-labs solana-pay, published on 1 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-35917 and fix it if it is affected.\n\nWhat it is: CVE-2022-35917 is a medium-severity vulnerability in solana-labs solana-pay, published on 1 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-35917 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @solana/pay (npm): affected all versions; fixed in 0.2.1\n- @solana/pay (npm): affected all versions; fixed in 0.2.1\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-2022-35917/ (Markdown: https://insights.sbomify.com/CVE-2022-35917/index.md)","id":"CVE-2022-35917","markdown":"https://insights.sbomify.com/CVE-2022-35917/index.md","name":"CVE-2022-35917","record":{"aliases":["GHSA-j47c-j42c-mwqq"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Solana Pay SDK","requires_auth":"none","summary":"Attackers can bypass transfer validation logic in the Solana Pay SDK, potentially allowing unauthorized or incorrect transaction processing.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"pay","vendor":"solanalabs"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-670","name":"Always-Incorrect Control Flow Implementation"}],"description":"Solana Pay is a protocol and set of reference implementations that enable developers to incorporate decentralized payments into their apps and services. When a Solana Pay transaction is located using a reference key, it may be checked to represent a transfer of the desired amount to the recipient, using the supplied `validateTransfer` function. An edge case regarding this mechanism could cause the validation logic to validate multiple transfers. This issue has been patched as of version `0.2.1`. Users of the Solana Pay SDK should upgrade to it. There are no known workarounds for this issue.","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":"Weakness in Transfer Validation Logic in @solana/pay","id":"CVE-2022-35917","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"business_logic","year":"2022"},"n_packages":2,"n_references":4,"next":{"headline":"Streamlit directory traversal vulnerability","id":"CVE-2022-35918"},"packages":[{"ecosystem":"npm","fixed":["0.2.1"],"introduced":["0"],"last_affected":[],"package":"@solana/pay","purl":null,"source":"GHSA-j47c-j42c-mwqq"},{"ecosystem":"npm","fixed":["0.2.1"],"introduced":["0"],"last_affected":[],"package":"@solana/pay","purl":"pkg:npm/%40solana/pay","source":"GHSA-j47c-j42c-mwqq"}],"prev":{"headline":"Cross chain utilities for Arbitrum L2 see EOA calls as cross chain calls","id":"CVE-2022-35916"},"products":["solana-pay"],"published":"2022-08-01","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["solana-labs"]},"summary":"Attackers can bypass transfer validation logic in the Solana Pay SDK, potentially allowing unauthorized or incorrect transaction processing.","url":"https://insights.sbomify.com/CVE-2022-35917/"}