Keyview IdolApplication · Autonomy

CVE-2012-6349

HIGH · 9.3 CVSS v2.0 Published 2013-07-18
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
Buffer overflow in the .mdb parser in Autonomy KeyView IDOL, as used in IBM Notes 8.5.x before 8.5.3 FP4, allows remote attackers to execute arbitrary code via a crafted file, aka SPR KLYH92XL3W.

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

Buffer overflow vulnerability in the .mdb file parser (Autonomy KeyView IDOL) in IBM Notes versions 8.5.x before 8.5.3 FP4 allows remote code execution via specially crafted Microsoft Database files.

MitigationUpgrade IBM Notes to version 8.5.3 FP4 or later. Until patched, block or quarantine untrusted .mdb file attachments.

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
Keyview IdolApplication
Affected:all versions
Lotus NotesApplication
Affected:= 8.5= 8.5.0.0= 8.5.0.1= 8.5.1= 8.5.1.0= 8.5.1.1= 8.5.1.2= 8.5.1.3= 8.5.1.4= 8.5.1.5= 8.5.2.0= 8.5.2.1

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 IBM Notes installation and version
    Open IBM Notes, go to Help > About IBM Notes, or right-click on notes.exe and select Properties > Details to see the version. Alternatively, check the Windows registry at HKEY_LOCAL_MACHINE\SOFTWARE\IBM\Notes or look in the Notes installation directory (typically C:\Program Files\IBM\Notes).
    Affected if The installed version is 8.5, 8.5.0.0, 8.5.0.1, 8.5.1, 8.5.1.0, 8.5.1.1, 8.5.1.2, 8.5.1.3, 8.5.1.4, 8.5.1.5, 8.5.2.0, or 8.5.2.1 (versions before 8.5.3 FP4).
  2. Verify Autonomy KeyView IDOL component presence
    Look for KeyView-related files in the IBM Notes program directory, typically under the 'keyview' or ' converters' subfolder. On Windows, check C:\Program Files\IBM\Notes\keyview\ or C:\Program Files\IBM\Notes\converters\.
    Affected if The KeyView IDOL component is present and bundled with the Notes installation (this is the vulnerable parser).
  3. Confirm .mdb attachment handling is enabled
    In IBM Notes, go to File > Preferences > Mail > MIME and check attachment handling settings, or verify that the conversion of .mdb files is enabled in the Domino server configuration if processing attachments server-side.
    Affected if IBM Notes is configured to process or preview .mdb file attachments (this is the default behavior enabling the attack vector).

You are affected if IBM Notes version 8.5.x before 8.5.3 FP4 is installed with the KeyView IDOL component present and .mdb file attachment 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade IBM Notes to version 8.5.3 FP4 or later. Until patched, block or quarantine untrusted .mdb file attachments.

Recommended fix High confidence

IBM Notes 8.5.3 FP4 or later

  1. 1. Check the current IBM Notes version by opening the application and navigating to Help > About IBM Notes
  2. 2. Create a full backup of the IBM Notes data directory, including mail files, contacts, and preferences
  3. 3. Download IBM Notes 8.5.3 FP4 (or a later version) from the official IBM Fix Central website (https://www-945.ibm.com/support/fixcentral/)
  4. 4. Close all IBM Notes applications and any related processes
  5. 5. Run the installer for IBM Notes 8.5.3 FP4 or later
  6. 6. Follow the installation wizard prompts, choosing the upgrade option to preserve existing data and settings
  7. 7. After installation, restart IBM Notes and verify the version by checking Help > About IBM Notes to confirm the fix is applied
Caveat Upgrading IBM Notes may require migration of existing mail files and templates; verify compatibility with existing Domino servers and third-party plugins before upgrading

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

Fix this in Keyview Idol 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 help mitigating

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-2012-6349 — 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-2012-6349 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