CVE-2024-41945

{"id": "CVE-2024-41945", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 3.1, "attackVector": "NETWORK", "baseSeverity": "LOW", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "NONE"}, "impactScore": 1.4, "exploitabilityScore": 1.6}]}, "published": "2024-07-30T20:15:04.930", "references": [{"url": "https://github.com/FuelLabs/fuels-ts/security/advisories/GHSA-3jcg-vx7f-j6qf", "source": "security-advisories@github.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-20"}]}], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "fuels-ts es una librer\u00eda para interactuar con Fuel v2. El SDK mecanografiado no tiene conocimiento de las transacciones que se van a gastar, lo que hace que algunas transacciones fallen o se eliminen silenciosamente, ya que se financian con UTXO ya usados. El problema ocurre porque la funci\u00f3n `fund` en `fuels-ts/packages/account/src/account.ts` obtiene los recursos necesarios sin estado con la funci\u00f3n `getResourcesToSpend` sin tener en cuenta los UTXO ya utilizados. Este problema provocar\u00e1 un comportamiento inesperado del SDK, como que una transacci\u00f3n no se incluya en `txpool`/en un bloque o que una transacci\u00f3n anterior se elimine silenciosamente de `txpool` y se reemplace por una nueva."}], "lastModified": "2024-07-31T12:57:02.300", "sourceIdentifier": "security-advisories@github.com"}