# CVE-2023-6017: H2O S3 Bucket Takeover

> An attacker can take over a dangling S3 bucket reference in H2O, potentially reading or modifying data stored there.

- **Severity:** High 8.7 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Nov 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-pwcm-766j-45vc

## What is CVE-2023-6017?

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.

### Official description

H2O included a reference to an S3 bucket that no longer existed allowing an attacker to take over the S3 bucket URL.

Weakness: CWE-840

## Which versions are affected by CVE-2023-6017?

It affects 1 product.


Products: H2o H2o.

## How do I fix CVE-2023-6017?

No fix has been published for CVE-2023-6017 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-6017 being exploited?

There is no known exploitation of CVE-2023-6017 in the wild and no public exploit code.

## Other vulnerabilities in h2oai/h2o-3

- [CVE-2023-6016](https://insights.sbomify.com/CVE-2023-6016/): H2O Remote Code Execution via POJO Model Import (critical 10.0)
- [CVE-2025-6544](https://insights.sbomify.com/CVE-2025-6544/): Deserialization Vulnerability in h2oai/h2o-3 (critical 9.8)
- [CVE-2024-10553](https://insights.sbomify.com/CVE-2024-10553/): Jdbc Deserialization in h2oai/h2o-3 (critical 9.8)
- [CVE-2023-6569](https://insights.sbomify.com/CVE-2023-6569/): External Control of File Name or Path in h2oai/h2o-3 (critical 9.3)
- [CVE-2023-6013](https://insights.sbomify.com/CVE-2023-6013/): H2O Local File Include (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-6017 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2023-6017 in the wild and no public exploit code.

Affected product: h2oai/h2o-3. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-6017/ (Markdown: https://insights.sbomify.com/CVE-2023-6017/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-6017
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-6017
- OSV: https://osv.dev/vulnerability/CVE-2023-6017

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-6017/
Summaries are generated and may contain mistakes; the official description above is the record.