dbcve.org
Lotus NotesApplication · Ibm

CVE-2007-5406

HIGH · 9.3 CVSS v2.0 Published 2008-04-10
Fix available
A fix is available. Upgrade to after 7.5 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
kpagrdr.dll 2.0.0.2 and 10.3.0.0 in the Applix Presents reader in Autonomy (formerly Verity) KeyView, as used by IBM Lotus Notes, Symantec Mail Security, and activePDF DocConverter, does not properly parse long tokens, which allows remote attackers to cause a denial of service (CPU and memory consumption) via a crafted .ag file.

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 · high confidence

The kpagrdr.dll library (versions 2.0.0.2 and 10.3.0.0) in Autonomy KeyView's Applix Presents reader fails to properly parse long tokens in .ag files, allowing remote attackers to trigger excessive CPU and memory consumption through malformed input files.

MitigationApply vendor patches from Autonomy/HP for KeyView, or update affected products (IBM Lotus Notes, Symantec Mail Security, activePDF DocConverter) to versions that include the patched library. Consider disabling .ag file processing in untrusted contexts until patches are applied.

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
Lotus NotesApplication
Affected:= 6.0= 6.5= 7.0= 8.0= 8.0.1
Mail SecurityApplication
Affected:<= 7.5= 5.0= 5.0.0= 5.0.1
KeyviewApplication
Affected:all versions

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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

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. Locate the kpagrdr.dll library on the system
    Search the filesystem for kpagrdr.dll (common locations include program directories, system32, or application-specific folders). Use 'dir /s /b C:\kpagrdr.dll' on Windows or 'find / -name kpagrdr.dll' on Unix-like systems.
    Affected if The DLL file exists on the system and its version is 2.0.0.2 or 10.3.0.0, or falls within the affected version range.
  2. Verify the installed version of kpagrdr.dll
    Right-click the DLL file, select Properties, then view the Details tab to see the File Version. Alternatively, use a tool like 'strings' or a hex editor to examine version metadata embedded in the file.
    Affected if The reported version matches 2.0.0.2 or 10.3.0.0, indicating the vulnerable library is present.
  3. Check if IBM Lotus Notes is installed
    Look for Lotus Notes in the system (common paths: C:\Program Files\IBM\Lotus\Notes or C:\Lotus\Notes). Check the installed programs list via Control Panel > Programs and Features, or check the version via the Notes executable.
    Affected if Lotus Notes versions 6.0, 6.5, 7.0, 8.0, or 8.0.1 are installed and the kpagrdr.dll library is present.
  4. Check if Symantec Mail Security is installed
    Look for Symantec Mail Security in the system (check Program Files\Symantec or Program Files\Symantec\Security*. Check installed programs or the application version via its GUI or registry entries.
    Affected if Symantec Mail Security versions 5.0, 5.0.0, 5.0.1, or any version <= 7.5 is installed and the kpagrdr.dll library is present.
  5. Determine if .ag file processing is active
    Check whether the KeyView filter, Lotus Notes, or Symantec Mail Security has .ag (Applix Presents) file type handlers configured or enabled. Look for file association settings or filter configurations in the respective applications.
    Affected if The system processes .ag files through the vulnerable library component, making it susceptible to the malformed input DoS.

The environment is affected if kpagrdr.dll version 2.0.0.2 or 10.3.0.0 is present, OR if any affected IBM Lotus Notes or Symantec Mail Security version is installed alongside the KeyView library, AND .ag file processing is enabled.

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.

From vendor data
Upgrade available Upgrade to a release after 7.5
Interim mitigation

Apply vendor patches from Autonomy/HP for KeyView, or update affected products (IBM Lotus Notes, Symantec Mail Security, activePDF DocConverter) to versions that include the patched library. Consider disabling .ag file processing in untrusted contexts until patches are applied.

Fix this in Lotus Notes Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-5406 — 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-2007-5406 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