dbcve.org
KeyviewApplication · Hp

CVE-2016-4404

CRITICAL · 9.8 CVSS v3.0 Published 2018-08-06
Fix available
A fix is available. Upgrade to 11.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
A security vulnerability was identified in the Filter SDK component of HP KeyView earlier than v11.2. The vulnerability could be exploited remotely to allow code execution via a memory allocation issue.

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 confidence

A memory allocation vulnerability in the Filter SDK component of HP KeyView versions prior to 11.2 allows remote attackers to execute arbitrary code. The memory allocation issue likely results in heap corruption or similar buffer overflow condition that can be triggered by processing specially crafted files.

MitigationUpgrade HP KeyView to version 11.2 or later to obtain the patched binaries. If immediate patching is not possible, restrict network exposure and sanitize untrusted input processed by the Filter SDK.

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
KeyviewApplication
Affected:< 11.2

CVSS 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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if HP KeyView is installed
    Search for HP KeyView installation directories or check system for KeyView executables, DLLs, or SDK components. Common locations include C:\Program Files\HP\KeyView or /opt/hp/keyview. Use 'dir /s C:\*keyview*' on Windows or 'find / -name *keyview*' on Linux.
    Affected if HP KeyView software is found on the system
  2. Determine the installed version
    Locate version information in the installation directory, such as a version.txt file, or right-click on key executable files (keyview.exe, kvfilter.dll) and check Properties > Details for version numbers. If using the SDK, check the SDK header files or accompanying documentation.
    Affected if No version number is displayed or the software reports a version below 11.2
  3. Compare version to affected range
    Document the exact version number found and compare it against the affected range: versions prior to 11.2. For example, versions 11.0, 10.x, or any 11.1.x build are all vulnerable.
    Affected if The installed version is any version number less than 11.2 (e.g., 11.1.0, 11.0.0, 10.x)
  4. Verify if Filter SDK component is in use
    Check if the Filter SDK or its components (kvfilter.dll, filterapi.dll, or similar filter-related DLLs) are present in the installation. Look for applications or services that call the Filter SDK API for file processing.
    Affected if Filter SDK components are present and being used to process files
  5. Check for untrusted file processing
    Review application logs or configuration to determine if the Filter SDK is configured to process files from untrusted or external sources. Look for file import/upload features that use KeyView for parsing.
    Affected if The Filter SDK is configured to parse, import, or process files from untrusted or external sources

The environment is affected if HP KeyView version 11.2 or later is NOT installed AND the Filter SDK is being used to process files, particularly from untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 11.2 or later
Fixed in 11.2
Interim mitigation

Upgrade HP KeyView to version 11.2 or later to obtain the patched binaries. If immediate patching is not possible, restrict network exposure and sanitize untrusted input processed by the Filter SDK.

Recommended fix High confidence

HP KeyView version 11.2

  1. Obtain HP KeyView version 11.2 or later from the official HPE software distribution portal
  2. Ensure all systems running KeyView Filter SDK are identified and documented
  3. Schedule a maintenance window for the upgrade process
  4. Download the KeyView 11.2 installation package from HPE Support (support.hpe.com)
  5. Backup existing KeyView installations and configurations before proceeding
  6. Install KeyView 11.2 on all affected systems following the HPE installation guide
  7. Verify the installation was successful by checking the KeyView version
  8. Test critical document processing workflows to ensure functionality is intact

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Keyview Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-4404 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-4404 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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