# CVE-2023-28711: Denial of service in Hyperscan Library maintained by Intel(R)

> An authenticated local user can cause a denial of service in the Hyperscan Library due to insufficient control flow management.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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:** Yes
- **Published:** 11 Aug 2023
- **Updated:** 2 Oct 2024
- **Also known as:** GHSA-95ch-mqcf-w529, OESA-2023-1609

## What is CVE-2023-28711?

CVE-2023-28711 is a medium-severity denial of service vulnerability in Hyperscan Library maintained by Intel(R), published on 11 Aug 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Insufficient control flow management in the Hyperscan Library maintained by Intel(R) before version 5.4.1 may allow an authenticated user to potentially enable denial of service via local access.

Weakness: CWE-670 (Always-Incorrect Control Flow Implementation), CWE-691 (Insufficient Control Flow Management)

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

It affects 1 product.


Products: Intel Hyperscan Library.

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

Upgrade to a fixed version.

## Is CVE-2023-28711 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-28711 is a medium-severity denial of service vulnerability in Hyperscan Library maintained by Intel(R), published on 11 Aug 2023. 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-28711 in the wild and no public exploit code.

Affected product: Hyperscan Library maintained by Intel(R). 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-28711/ (Markdown: https://insights.sbomify.com/CVE-2023-28711/index.md)
```

## Sources

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

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