CVE-2016-4387
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 · uneditedThe Filter SDK in HPE KeyView 10.18 through 10.24 allows remote attackers to execute arbitrary code via unspecified vectors, a different vulnerability than CVE-2016-4388, CVE-2016-4389, and CVE-2016-4390.
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 confidenceHPE KeyView Filter SDK versions 10.18 through 10.24 contains a remote code execution vulnerability. The vulnerability allows remote attackers to execute arbitrary code via unspecified vectors in the Filter SDK component. This is a critical severity issue (CVSS 8.1) affecting a widely-used file parsing and content extraction 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= 10.18.0.0= 10.19.0.0= 10.20.0.0= 10.21.0.0= 10.22.0.0= 10.23.0.0= 10.24.0.0CVSS 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
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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 HPE KeyView installationSearch for KeyView-related directories or files on the system. Common locations include /opt/hp/keyview or C:\Program Files\HPE\KeyView. Check for any installed packages or applications referencing KeyView.Affected if HPE KeyView Filter SDK is found on the system
-
Identify the installed KeyView versionLocate the version information file, use the application's version display option, or run 'pkginfo' (Solaris), 'rpm -qi' (Linux), or check Windows registry entries if KeyView was installed as a Windows application.Affected if The installed version matches 10.18.0.0 through 10.24.0.0 inclusive
-
Verify the Filter SDK component is deployedCheck for the presence of Filter SDK libraries, executables, or APIs within the KeyView installation directory. Look for directories named 'filter', 'filtersdk', or similar.Affected if The Filter SDK component is present and in use
-
Check for active KeyView services or processesReview running processes or services that may be utilizing KeyView for file parsing. Check system process lists and any documented KeyView service names.Affected if KeyView Filter SDK processes or services are running
A user is affected if HPE KeyView Filter SDK versions 10.18.0.0 through 10.24.0.0 are installed and the Filter SDK component is deployed on their system.
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.
From vendor dataApply the vendor-supplied patch for HPE KeyView to upgrade beyond version 10.24. If immediate patching is not possible, network segmentation and restricting access to systems using the KeyView Filter SDK may reduce exposure to remote exploitation.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-4387 — 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-2016-4387 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