# CVE-2024-33617: Information disclosure in Intel(R) QAT Engine for OpenSSL software

> An attacker with network access can exploit insufficient control flow management in the Intel QAT Engine for OpenSSL to disclose sensitive information.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Nov 2024
- **Updated:** 14 Nov 2024
- **Also known as:** GHSA-5p69-3rp7-542w

## What is CVE-2024-33617?

CVE-2024-33617 is a high-severity vulnerability in Intel(R) QAT Engine for OpenSSL software, published on 13 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Insufficient control flow management in some Intel(R) QAT Engine for OpenSSL software before version v1.6.1 may allow information disclosure via network access.

Weakness: CWE-691 (Insufficient Control Flow Management)

## Which versions are affected by CVE-2024-33617?


## How do I fix CVE-2024-33617?

Upgrade to a fixed version.

## Is CVE-2024-33617 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-33617 and fix it if it is affected.

What it is: CVE-2024-33617 is a high-severity vulnerability in Intel(R) QAT Engine for OpenSSL software, published on 13 Nov 2024. 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-2024-33617 in the wild and no public exploit code.

Affected product: Intel(R) QAT Engine for OpenSSL software. 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-2024-33617/ (Markdown: https://insights.sbomify.com/CVE-2024-33617/index.md)
```

## Sources

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

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