{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-42448 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-42448 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-42448 is a high-severity vulnerability in input-output-hk hydra, published on 4 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-42448 and fix it if it is affected.\n\nWhat it is: CVE-2023-42448 is a high-severity vulnerability in input-output-hk hydra, published on 4 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-42448 in the wild and no public exploit code.\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-42448/ (Markdown: https://insights.sbomify.com/CVE-2023-42448/index.md)","id":"CVE-2023-42448","markdown":"https://insights.sbomify.com/CVE-2023-42448/index.md","name":"CVE-2023-42448","record":{"aliases":["GHSA-mgcx-6p7h-5996"],"analysis":{"component_type":"other","fix_type":"upgrade","impacts":["data_modify","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Cardano layer-two solution","requires_auth":"low_privilege","summary":"A malicious participant can modify the contestation deadline during a Close transaction, allowing unauthorized fund distribution or blocking fund redistribution in Hydra.","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":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-1284","name":"Improper Validation of Specified Quantity in Input"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Hydra is the layer-two scalability solution for Cardano. Prior to version 0.13.0, the specification states that the contestation period in the datum of the UTxO at the head validator must stay unchanged as the state progresses from Open to Closed (Close transaction), but no such check appears to be performed in the `checkClose` function of the head validator. This would allow a malicious participant to modify the contestation deadline of the head to either allow them to fanout the head without giving another participant the chance to contest, or prevent any participant from ever redistributing the funds locked in the head via a fan-out. Version 0.13.0 contains a patch for this issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Business logic in hydra","id":"CVE-2023-42448","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2023"},"n_packages":0,"n_references":5,"next":{"headline":"Business logic in hydra","id":"CVE-2023-42449"},"packages":[],"prev":{"headline":"blurhash panics on parsing crafted inputs","id":"CVE-2023-42447"},"products":["hydra"],"published":"2023-10-04","related":[{"cvss_score":9.1,"headline":"Hydra's committed UTxOs at Commit validator and UTxOs at Initial validator can be spent arbitrarily by anyone","id":"CVE-2023-38701","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-09-19","vendors":["input-output-hk"]},"summary":"A malicious participant can modify the contestation deadline during a Close transaction, allowing unauthorized fund distribution or blocking fund redistribution in Hydra.","url":"https://insights.sbomify.com/CVE-2023-42448/"}