# CVE-2023-32011: Windows iSCSI Discovery Service Denial of Service Vulnerability

> An attacker can cause a denial of service in the Windows iSCSI Discovery Service via an out-of-bounds read vulnerability.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jun 2023
- **Updated:** 1 Jan 2025
- **Also known as:** GHSA-f4xh-5ghw-6265

## What is CVE-2023-32011?

CVE-2023-32011 is a high-severity denial of service vulnerability in Microsoft Windows 10 1507, published on 13 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Windows iSCSI Discovery Service Denial of Service Vulnerability

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 12 products.


Products: Microsoft Windows 10 1507, Microsoft Windows 10 1607, Microsoft Windows 10 1809, Microsoft Windows 10 21h2, Microsoft Windows 10 22h2, Microsoft Windows 11 21h2, Microsoft Windows 11 22h2, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Server 2016, Microsoft Windows Server 2019, Microsoft Windows Server 2022.

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

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

## Is CVE-2023-32011 being exploited?

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

## Other vulnerabilities in Microsoft Windows 10 1507

- [CVE-2017-8543](https://insights.sbomify.com/CVE-2017-8543/): Microsoft Windows Search Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2025-33053](https://insights.sbomify.com/CVE-2025-33053/): Microsoft Windows External Control of File Name or Path (high 8.8, exploited in the wild)
- [CVE-2025-33073](https://insights.sbomify.com/CVE-2025-33073/): Microsoft Windows SMB Client Improper Access Control (high 8.8, exploited in the wild)
- [CVE-2024-49039](https://insights.sbomify.com/CVE-2024-49039/): Microsoft Windows Task Scheduler Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2024-43461](https://insights.sbomify.com/CVE-2024-43461/): Microsoft Windows MSHTML Platform Spoofing (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-32011 is a high-severity denial of service vulnerability in Microsoft Windows 10 1507, published on 13 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-32011 in the wild and no public exploit code.

Affected product: Microsoft Windows 10 1507. 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-32011/ (Markdown: https://insights.sbomify.com/CVE-2023-32011/index.md)
```

## Sources

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

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