CVE-2023-28711
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInsufficient 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceInsufficient control flow management in the Intel Hyperscan Library before version 5.4.1 allows an authenticated local user to potentially cause a denial of service. The vulnerability stems from improper handling of control flow within the library.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 5.4.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate Intel Hyperscan Library installationSearch for hyperscan library files on the system. Common locations include /usr/lib/, /usr/local/lib/, or within application bundles. Look for files named libhs.so, libhs.a, or similar hyperscan library binaries.Affected if The library files are present on the system
-
Identify installed hyperscan versionRun 'strings' on the library file or use 'ldd -v' if linked, or check any version information in the library's metadata. You may also check the application's dependency list if hyperscan is linked statically.Affected if Version cannot be determined or is reported as below 5.4.1
-
Confirm library is actively loaded or usedCheck running processes or application configurations that reference or link to the hyperscan library. Examine application logs or dependency files (like .so files or build manifests) that indicate hyperscan is in use.Affected if The library is loaded or referenced by any application on the system
-
Verify vulnerability trigger conditionsThis is a local denial of service vulnerability requiring authenticated local access. Check if untrusted local users have access to systems where hyperscan is deployed.Affected if Untrusted local users have access to the system where hyperscan is installed
If Intel Hyperscan Library is installed and its version is determined to be lower than 5.4.1, the environment is affected by this vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped5.4.1
Upgrade the Hyperscan Library to version 5.4.1 or later to address the control flow management issue.
5.4.1
- Identify the current installed version of the Hyperscan Library in your environment
- Locate and obtain Hyperscan Library version 5.4.1 or later from the official Intel source or your distribution's package repository
- Replace or upgrade the existing Hyperscan Library installation to version 5.4.1 or newer
- Verify the upgraded version matches the target (5.4.1 or later) using the library's version reporting mechanism
- Test that dependent applications or services function correctly with the updated library
- Restart any services or processes that depend on the Hyperscan Library to ensure the new version is loaded
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation3.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,128.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28711 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-28711 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data