# CVE-2023-46159: IBM Storage Ceph denial of service

> An authenticated network user can cause a denial of service in IBM Storage Ceph RGW, requiring patches for affected deployments.

- **Severity:** Low 2.6 (`CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Feb 2024
- **Updated:** 22 Aug 2024
- **Also known as:** GHSA-p56v-8px4-hjvv, OESA-2024-2372, OESA-2024-2373, OESA-2024-2406

## What is CVE-2023-46159?

CVE-2023-46159 is a low-severity denial of service vulnerability in IBM Storage Ceph, published on 2 Feb 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IBM Storage Ceph 5.3z1, 5.3z5, and 6.1z1 could allow an authenticated user on the network to cause a denial of service from RGW.  IBM X-Force ID:  268906.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Ibm Storage Ceph.

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

Apply the vendor's patch.

## Is CVE-2023-46159 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-46159 is a low-severity denial of service vulnerability in IBM Storage Ceph, published on 2 Feb 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-46159 in the wild and no public exploit code.

Affected product: IBM Storage Ceph. 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-46159/ (Markdown: https://insights.sbomify.com/CVE-2023-46159/index.md)
```

## Sources

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

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