{"answers":{"affected":"2 open source packages ship an affected version, including @fuel-ts/account.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-41945 exists.","fix":"Upgrade @fuel-ts/account to 0.93.0 or later.","what":"CVE-2024-41945 is a low-severity vulnerability in FuelLabs fuels-ts, published on 30 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-41945 and fix it if it is affected.\n\nWhat it is: CVE-2024-41945 is a low-severity vulnerability in FuelLabs fuels-ts, published on 30 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-41945 exists.\n\nAffected packages and fixed versions:\n- @fuel-ts/account (npm): affected all versions; fixed in 0.93.0\n- @fuel-ts/account (npm): affected all versions; fixed in 0.93.0\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-2024-41945/ (Markdown: https://insights.sbomify.com/CVE-2024-41945/index.md)","id":"CVE-2024-41945","markdown":"https://insights.sbomify.com/CVE-2024-41945/index.md","name":"CVE-2024-41945","record":{"aliases":["GHSA-3jcg-vx7f-j6qf"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Fuel TypeScript SDK","requires_auth":"low_privilege","summary":"The Fuel TypeScript SDK fails to track spent UTXOs, causing transactions to fail or be silently pruned from the mempool.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":3.1,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"fuels-ts is a library for interacting with Fuel v2.  The typescript SDK has no awareness of to-be-spent transactions causing some transactions to fail or silently get pruned as they are funded with already used UTXOs. The problem occurs, because the `fund` function in `fuels-ts/packages/account/src/account.ts` gets the needed ressources statelessly with the function `getResourcesToSpend` without taking into consideration already used UTXOs. This issue will lead to unexpected SDK behaviour, such as a transaction not getting included in the `txpool` / in a block or a previous transaction silently getting removed from the `txpool` and replaced with a new one.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"The fuels-ts typescript SDK has no awareness of to-be-spent transactions","id":"CVE-2024-41945","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"business_logic","year":"2024"},"n_packages":2,"n_references":1,"next":{"headline":"REXML DoS vulnerability","id":"CVE-2024-41946"},"packages":[{"ecosystem":"npm","fixed":["0.93.0"],"introduced":["0"],"last_affected":[],"package":"@fuel-ts/account","purl":null,"source":"GHSA-3jcg-vx7f-j6qf"},{"ecosystem":"npm","fixed":["0.93.0"],"introduced":["0"],"last_affected":[],"package":"@fuel-ts/account","purl":"pkg:npm/%40fuel-ts/account","source":"GHSA-3jcg-vx7f-j6qf"}],"prev":{"headline":"Sensitive Information Disclosure abusing SQL Injection in Xibo CMS proof of play report","id":"CVE-2024-41944"},"products":["fuels-ts"],"published":"2024-07-30","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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["FuelLabs"]},"summary":"The Fuel TypeScript SDK fails to track spent UTXOs, causing transactions to fail or be silently pruned from the mempool.","url":"https://insights.sbomify.com/CVE-2024-41945/"}