CVE-2023-28711
Intel Hyperscan Library ≤ 5.4.1
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HSummary
CVE-2023-28711 is a medium-severity Insufficient Control Flow Management (CWE-691) vulnerability in Intel Hyperscan Library. Its CVSS base score is 5.5 (Medium).
Operationally, ranked at the 6th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-32349
Vulnerability Data
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.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 2 hardening rules · 2 OS baselines
V9.2.1
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Design principles and implementation approaches enforce robust control-flow management to maintain function and enable recovery after disruption.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC activities such as static analysis, code review, and testing directly prevent control-flow weaknesses while also addressing many other coding defects.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development and acceptance can detect control-flow weaknesses but does not itself implement preventive controls.
Secure development life cycle mandates structured control-flow design and review that directly reduces unexpected flow manipulation.
Secure system architecture and engineering principles require explicit control-flow integrity mechanisms and error-handling paths.
Secure coding standards explicitly forbid constructs that allow unintended control-flow changes such as missing breaks or unsafe jumps.
Change management reduces introduction of control-flow defects through controlled updates but does not address the weakness directly.