{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-6017 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-6017 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-6017 is a high-severity vulnerability in h2oai/h2o-3, published on 16 Nov 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-6017 and fix it if it is affected.\n\nWhat it is: CVE-2023-6017 is a high-severity vulnerability in h2oai/h2o-3, published on 16 Nov 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-6017 in the wild and no public exploit code.\n\nAffected product: h2oai/h2o-3. 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-6017/ (Markdown: https://insights.sbomify.com/CVE-2023-6017/index.md)","id":"CVE-2023-6017","markdown":"https://insights.sbomify.com/CVE-2023-6017/index.md","name":"CVE-2023-6017","record":{"aliases":["GHSA-pwcm-766j-45vc"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"H2O AI library","requires_auth":"low_privilege","summary":"An attacker can take over a dangling S3 bucket reference in H2O, potentially reading or modifying data stored there.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"h2o","vendor":"h2o"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-840","name":null}],"description":"H2O included a reference to an S3 bucket that no longer existed allowing an attacker to take over the S3 bucket URL.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"H2O S3 Bucket Takeover","id":"CVE-2023-6017","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"MLflow Arbitrary File Write","id":"CVE-2023-6018"},"packages":[],"prev":{"headline":"H2O Remote Code Execution via POJO Model Import","id":"CVE-2023-6016"},"products":["h2oai/h2o-3"],"published":"2023-11-16","related":[{"cvss_score":10,"headline":"H2O Remote Code Execution via POJO Model Import","id":"CVE-2023-6016","kev_date_added":null,"published":"2023-11-16"},{"cvss_score":9.8,"headline":"Deserialization Vulnerability in h2oai/h2o-3","id":"CVE-2025-6544","kev_date_added":null,"published":"2025-09-21"},{"cvss_score":9.8,"headline":"Jdbc Deserialization in h2oai/h2o-3","id":"CVE-2024-10553","kev_date_added":null,"published":"2025-03-20"},{"cvss_score":9.3,"headline":"External Control of File Name or Path in h2oai/h2o-3","id":"CVE-2023-6569","kev_date_added":null,"published":"2023-12-14"},{"cvss_score":9.3,"headline":"H2O Local File Include","id":"CVE-2023-6013","kev_date_added":null,"published":"2023-11-16"},{"cvss_score":9.3,"headline":"Local File Inclusion in h2oai/h2o-3","id":"CVE-2023-6038","kev_date_added":null,"published":"2023-11-16"},{"cvss_score":9.1,"headline":"H2O.ai H2O vulnerable to deserialization attacks via a JDBC Connection URL","id":"CVE-2024-45758","kev_date_added":null,"published":"2024-09-06"}],"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":["h2oai"]},"summary":"An attacker can take over a dangling S3 bucket reference in H2O, potentially reading or modifying data stored there.","url":"https://insights.sbomify.com/CVE-2023-6017/"}