{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-50247 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-50247 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-50247 is a low-severity denial of service vulnerability in h2o, published on 12 Dec 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-50247 and fix it if it is affected.\n\nWhat it is: CVE-2023-50247 is a low-severity denial of service vulnerability in h2o, published on 12 Dec 2023. 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-2023-50247 in the wild and no public exploit code.\n\nAffected product: h2o. 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-50247/ (Markdown: https://insights.sbomify.com/CVE-2023-50247/index.md)","id":"CVE-2023-50247","markdown":"https://insights.sbomify.com/CVE-2023-50247/index.md","name":"CVE-2023-50247","record":{"aliases":["GHSA-2ch5-p59c-7mv6"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"h2o HTTP server","requires_auth":"none","summary":"Remote attackers can exhaust memory in h2o's QUIC stack when HTTP/3 is enabled, causing a denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"h2o","vendor":"dena"}],"cvss":{"score":3.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"h2o is an HTTP server with support for HTTP/1.x, HTTP/2 and HTTP/3. The QUIC stack (quicly), as used by H2O up to commit 43f86e5 (in version 2.3.0-beta and prior), is susceptible to a state exhaustion attack. When H2O is serving HTTP/3, a remote attacker can exploit this vulnerability to progressively increase the memory retained by the QUIC stack. This can eventually cause H2O to abort due to memory exhaustion. The vulnerability has been resolved in commit d67e81d03be12a9d53dc8271af6530f40164cd35. HTTP/1 and HTTP/2 are not affected by this vulnerability as they do not use QUIC. Administrators looking to mitigate this issue without upgrading can disable HTTP/3 support.","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":"h2o QUIC state exhaustion DoS","id":"CVE-2023-50247","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"CKAN out of memory error when submitting the dataset form with a specially-crafted field","id":"CVE-2023-50248"},"packages":[],"prev":{"headline":"jq has heap-buffer-overflow vulnerability in the function decToString in decNumber.c","id":"CVE-2023-50246"},"products":["h2o"],"published":"2023-12-12","related":[{"cvss_score":9.8,"headline":"Memory corruption in H2O","id":"CVE-2018-0608","kev_date_added":null,"published":"2018-06-26"},{"cvss_score":9.1,"headline":"Use after free in H2O","id":"CVE-2016-7835","kev_date_added":null,"published":"2017-06-09"},{"cvss_score":8.2,"headline":"H2O vulnerable to read from uninitialized pointer in the reverse proxy handler","id":"CVE-2023-30847","kev_date_added":null,"published":"2023-04-27"},{"cvss_score":7.5,"headline":"Denial of service in H2O","id":"CVE-2017-10868","kev_date_added":null,"published":"2017-12-22"},{"cvss_score":7.5,"headline":"Memory corruption in H2O","id":"CVE-2017-10869","kev_date_added":null,"published":"2017-12-22"},{"cvss_score":7.5,"headline":"Denial of service in H2O","id":"CVE-2017-10908","kev_date_added":null,"published":"2017-12-22"},{"cvss_score":7.5,"headline":"Denial of service in H2O","id":"CVE-2016-4864","kev_date_added":null,"published":"2017-05-12"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-02","vendors":["h2o"]},"summary":"Remote attackers can exhaust memory in h2o's QUIC stack when HTTP/3 is enabled, causing a denial of service.","url":"https://insights.sbomify.com/CVE-2023-50247/"}