dbcve.org
Lotus SymphonyApplication · Ibm

CVE-2012-0192

HIGH · 9.3 CVSS v2.0 Published 2012-01-23
Fix available
A fix is available. Upgrade to after 3.0.0.3 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
Multiple integer overflows in vclmi.dll in the visual class library module in IBM Lotus Symphony before 3.0.1 might allow remote attackers to execute arbitrary code via an embedded (1) JPEG or (2) PNG image object in a Symphony document that triggers a heap-based buffer overflow, as demonstrated by a .doc 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

Integer overflows in the vclmi.dll visual class library module allow heap-based buffer overflows when processing embedded JPEG or PNG images in IBM Lotus Symphony documents. Attackers can craft malicious .doc files containing oversized image dimensions that trigger the overflow, enabling arbitrary code execution.

MitigationUpgrade IBM Lotus Symphony to version 3.0.1 or later to patch the vulnerable vclmi.dll component. Avoid opening untrusted .doc files from unknown sources until the upgrade is 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 SymphonyApplication
Affected:<= 3.0.0.3= 1.3= 3.0.0.1= 3.0.0.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
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. Confirm IBM Lotus Symphony installation
    Locate the IBM Lotus Symphony installation directory (typically C:\Program Files\IBM\Lotus Symphony\ or C:\Program Files\IBM\Lotus Symphony\) or check Windows Registry under HKLM\SOFTWARE\IBM\Lotus Symphony for installation evidence
    Affected if IBM Lotus Symphony is not installed on the system
  2. Identify installed version
    Check the version information of the lotus.exe binary in the installation directory, or query the Windows Registry key HKLM\SOFTWARE\IBM\Lotus Symphony\Version if present
    Affected if The installed version is 1.3, 3.0.0.1, 3.0.0.2, or any version up to and including 3.0.0.3
  3. Locate vulnerable vclmi.dll component
    Search for vclmi.dll within the IBM Lotus Symphony installation folder, typically found in the program directory or a subfolder such as \program files\IBM\Lotus Symphony\
    Affected if The vclmi.dll file exists in the IBM Lotus Symphony installation directory (vulnerable component is present)
  4. Determine exposure to untrusted documents
    Review whether users routinely open .doc files from untrusted or unknown sources using IBM Lotus Symphony, or check recent document history
    Affected if Users open .doc files from untrusted sources using the vulnerable Lotus Symphony version

A system is affected if IBM Lotus Symphony version 1.3, 3.0.0.1, 3.0.0.2, or any version through 3.0.0.3 is installed and users open .doc files containing embedded images with the vulnerable vclmi.dll component.

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 a release after 3.0.0.3
Interim mitigation

Upgrade IBM Lotus Symphony to version 3.0.1 or later to patch the vulnerable vclmi.dll component. Avoid opening untrusted .doc files from unknown sources until the upgrade is applied.

Recommended fix High confidence

IBM Lotus Symphony 3.0.1 or later

  1. 1. Back up all important IBM Lotus Symphony documents and settings
  2. 2. Uninstall the current version of IBM Lotus Symphony from the system
  3. 3. Download IBM Lotus Symphony version 3.0.1 or later from the official IBM website or authorized distribution channel
  4. 4. Install IBM Lotus Symphony 3.0.1 using standard installation procedures
  5. 5. Verify the installation by checking the application version (typically via Help > About IBM Lotus Symphony)
  6. 6. Re-open previously created Symphony documents to ensure compatibility

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

Fix this in Lotus Symphony Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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