# CVE-2023-41252: Denial of service in Intel(R) QAT software drivers for Windows

> An authenticated local attacker can cause a denial of service via an out-of-bounds read in Intel QAT Windows drivers.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H`)
- **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:** No
- **Published:** 14 Feb 2024
- **Updated:** 16 Aug 2024

## What is CVE-2023-41252?

CVE-2023-41252 is a medium-severity denial of service vulnerability in Intel(R) QAT software drivers for Windows, published on 14 Feb 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Out-of-bounds read in some Intel(R) QAT software drivers for Windows before version QAT1.7-W-1.11.0 may allow an authenticated user to potentially enable denial of service via local access.

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

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

It affects 1 product.


Products: Intel Quickassist Technology Driver.

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

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

## Is CVE-2023-41252 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-41252 is a medium-severity denial of service vulnerability in Intel(R) QAT software drivers for Windows, published on 14 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-41252 in the wild and no public exploit code.

Affected product: Intel(R) QAT software drivers for Windows. 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-41252/ (Markdown: https://insights.sbomify.com/CVE-2023-41252/index.md)
```

## Sources

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

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