{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-30847 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-30847 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-30847 is a high-severity vulnerability in h2o, published on 27 Apr 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-30847 and fix it if it is affected.\n\nWhat it is: CVE-2023-30847 is a high-severity vulnerability in h2o, published on 27 Apr 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-30847 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-30847/ (Markdown: https://insights.sbomify.com/CVE-2023-30847/index.md)","id":"CVE-2023-30847","markdown":"https://insights.sbomify.com/CVE-2023-30847/index.md","name":"CVE-2023-30847","record":{"aliases":["GHSA-p5hj-phwj-hrvx","UBUNTU-CVE-2023-30847"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"H2O HTTP server","requires_auth":"none","summary":"An attacker can cause crashes or leak sensitive information to backend servers by sending invalid HTTP requests to the H2O reverse proxy handler.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"h2o","vendor":"dena"}],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-824","name":"Access of Uninitialized Pointer"}],"description":"H2O is an HTTP server. In versions 2.3.0-beta2 and prior, when the reverse proxy handler tries to processes a certain type of invalid HTTP request, it tries to build an upstream URL by reading from uninitialized pointer. This behavior can lead to crashes or leak of information to back end HTTP servers. Pull request  number 3229 fixes the issue. The pull request has been merged to the `master` branch in commit f010336. Users should upgrade to commit f010336 or later.","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 vulnerable to read from uninitialized pointer in the reverse proxy handler","id":"CVE-2023-30847","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"Pimcore SQL Injection Vulnerability in Admin Search Find API","id":"CVE-2023-30848"},"packages":[],"prev":{"headline":"typed-rest-client vulnerable to potential leak of authentication data to 3rd parties","id":"CVE-2023-30846"},"products":["h2o"],"published":"2023-04-27","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":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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-01-30","vendors":["h2o"]},"summary":"An attacker can cause crashes or leak sensitive information to backend servers by sending invalid HTTP requests to the H2O reverse proxy handler.","url":"https://insights.sbomify.com/CVE-2023-30847/"}