{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-45402 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-45402 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-45402 is a high-severity use after free vulnerability in h2o picotls, published on 11 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-45402 and fix it if it is affected.\n\nWhat it is: CVE-2024-45402 is a high-severity use after free vulnerability in h2o picotls, published on 11 Oct 2024. 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-2024-45402 in the wild and no public exploit code.\n\nAffected product: h2o picotls. 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-2024-45402/ (Markdown: https://insights.sbomify.com/CVE-2024-45402/index.md)","id":"CVE-2024-45402","markdown":"https://insights.sbomify.com/CVE-2024-45402/index.md","name":"CVE-2024-45402","record":{"aliases":["GHSA-w7c8-wjx9-vvvv"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"TLS protocol library","requires_auth":"none","summary":"A double free in picotls during TLS handshake parsing can lead to use-after-free, potentially allowing arbitrary code execution or denial of service.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"picotls","vendor":"dena"}],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H","version":"3.1"},"cwes":[{"id":"CWE-415","name":"Double Free"}],"description":"Picotls is a TLS protocol library that allows users select different crypto backends based on their use case. When parsing a spoofed TLS handshake message, picotls (specifically, bindings within picotls that call the crypto libraries) may attempt to free the same memory twice. This double free occurs during the disposal of multiple objects without any intervening calls to malloc Typically, this triggers the malloc implementation to detect the error and abort the process. However, depending on the internals of malloc and the crypto backend being used, the flaw could potentially lead to a use-after-free scenario, which might allow for arbitrary code execution. The vulnerability is addressed with commit 9b88159ce763d680e4a13b6e8f3171ae923a535d.","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":"Picotls double free","id":"CVE-2024-45402","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"H2O assertion failure when HTTP/3 requests are cancelled","id":"CVE-2024-45403"},"packages":[],"prev":{"headline":"stripe-cli Path Traversal vulnerability","id":"CVE-2024-45401"},"products":["picotls"],"published":"2024-10-11","related":[],"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-10-15","vendors":["h2o"]},"summary":"A double free in picotls during TLS handshake parsing can lead to use-after-free, potentially allowing arbitrary code execution or denial of service.","url":"https://insights.sbomify.com/CVE-2024-45402/"}