KeyviewApplication · Autonomy

CVE-2008-0066

HIGH · 9.3 CVSS v2.0 Published 2008-04-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Multiple buffer overflows in htmsr.dll in the HTML speed reader in Autonomy (formerly Verity) KeyView, as used by IBM Lotus Notes 7.0.2 and 7.0.3, allow remote attackers to execute arbitrary code via an HTML document with (1) "large chunks of data," or a long URL in the (2) BACKGROUND attribute of a BODY element or (3) SRC attribute of an IMG element.

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

Multiple buffer overflow vulnerabilities exist in htmsr.dll (HTML speed reader) in Autonomy KeyView, as used by IBM Lotus Notes 7.0.2 and 7.0.3. Attackers can achieve remote code execution by crafting malicious HTML documents containing oversized data in the BODY element's BACKGROUND attribute or the IMG element's SRC attribute.

MitigationApply the appropriate IBM Lotus Notes security patch for this vulnerability. Until patched, users should avoid opening untrusted HTML documents or disable HTML preview/rendering in Lotus Notes.

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:all versions
Lotus NotesApplication
Affected:= 7.0.2= 7.0.3

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. Check if IBM Lotus Notes is installed
    Look for IBM Lotus Notes installation directory, typically in C:\Program Files\IBM\Lotus\Notes or C:\Lotus\Notes. Alternatively, check Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Lotus\Notes or HKEY_CURRENT_USER\SOFTWARE\Lotus\Notes for the Notes installation path.
    Affected if IBM Lotus Notes is not installed on the system
  2. Verify the Lotus Notes version
    Check the version of the installed IBM Lotus Notes by examining the executable properties. Right-click on notes.exe in the installation directory and view the Details tab, or run 'notes.exe -version' from command line if supported. Compare against the affected versions 7.0.2 and 7.0.3.
    Affected if The installed version is exactly 7.0.2 or 7.0.3
  3. Confirm the vulnerable htmsr.dll component exists
    Search for htmsr.dll within the Lotus Notes installation directory and subfolders, typically under the "notes\html" or "notes" directory. The file should exist if KeyView HTML speed reader functionality is present.
    Affected if htmsr.dll exists in the Lotus Notes installation path
  4. Determine if HTML preview or rendering is enabled
    In Lotus Notes, go to File > Preferences > Trust Sites > External Links or check the Notes.ini configuration file for settings like "HTML_SR_Enable" or similar preview-related parameters. Also verify if the preview pane is active for HTML email attachments.
    Affected if HTML preview, rendering, or external content display is enabled in Lotus Notes settings

A user is affected if they have IBM Lotus Notes version 7.0.2 or 7.0.3 installed with the htmsr.dll component present and HTML preview/rendering functionality 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the appropriate IBM Lotus Notes security patch for this vulnerability. Until patched, users should avoid opening untrusted HTML documents or disable HTML preview/rendering in Lotus Notes.

Fix this in Keyview Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2008-0066 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2008-0066 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