{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-38701 exists.","fix":"No fix has been published for CVE-2023-38701 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-38701 is a critical vulnerability in input-output-hk hydra, published on 4 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-38701 and fix it if it is affected.\n\nWhat it is: CVE-2023-38701 is a critical vulnerability in input-output-hk hydra, published on 4 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-38701 exists.\n\nAffected product: input-output-hk hydra. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2023-38701/ (Markdown: https://insights.sbomify.com/CVE-2023-38701/index.md)","id":"CVE-2023-38701","markdown":"https://insights.sbomify.com/CVE-2023-38701/index.md","name":"CVE-2023-38701","record":{"aliases":["GHSA-6x9v-7x5r-w8w6"],"analysis":{"component_type":"other","fix_type":"upgrade","impacts":["data_modify","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Cardano Layer-2 solution","requires_auth":"none","summary":"Attackers can steal committed funds and block head initialization due to flawed validator checks in the Hydra protocol.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"hydra","vendor":"iohk"}],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Hydra is the layer-two scalability solution for Cardano. Users of the Hydra head protocol send the UTxOs they wish to commit into the Hydra head first to the `commit` validator, where they remain until they are either collected into the `head` validator or the protocol initialisation is aborted and the value in the committed UTxOs is returned to the users who committed them. Prior to version 0.12.0, the `commit` validator contains a flawed check when the `ViaAbort` redeemer is used, which allows any user to spend any UTxO which is at the validator arbitrarily, meaning an attacker can steal the funds that users are trying to commit into the head validator. The intended behavior is that the funds must be returned to the user which committed the funds and can only be performed by a participant of the head. The `initial` validator also is similarly affected as the same flawed check is performed for the `ViaAbort` redeemer. Due to this issue, an attacker can steal any funds that user's try to commit into a Hydra head. Also, an attacker can prevent any Hydra head from being successfully opened. It does not allow an attacker to take funds which have been successfully collected into and currently reside in the `head` validator. Version 0.12.0 contains a fix for this issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Hydra's committed UTxOs at Commit validator and UTxOs at Initial validator can be spent arbitrarily by anyone","id":"CVE-2023-38701","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2023"},"n_packages":0,"n_references":4,"next":{"headline":"Knowage Server vulnerable to path traversal via upload functionality","id":"CVE-2023-38702"},"packages":[],"prev":{"headline":"matrix-appservice-irc events can be crafted to leak parts of targeted messages from other bridged rooms","id":"CVE-2023-38700"},"products":["hydra"],"published":"2023-10-04","related":[{"cvss_score":8.1,"headline":"Business logic in hydra","id":"CVE-2023-42448","kev_date_added":null,"published":"2023-10-04"},{"cvss_score":8.1,"headline":"Business logic in hydra","id":"CVE-2023-42449","kev_date_added":null,"published":"2023-10-04"},{"cvss_score":6.5,"headline":"Snapshot signature not including HeadID will allow replay attacks","id":"CVE-2023-42806","kev_date_added":null,"published":"2023-09-21"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-09-19","vendors":["input-output-hk"]},"summary":"Attackers can steal committed funds and block head initialization due to flawed validator checks in the Hydra protocol.","url":"https://insights.sbomify.com/CVE-2023-38701/"}