CVE-2010-5204
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 · uneditedMultiple untrusted search path vulnerabilities in IBM Lotus Symphony 1.3.0 20090908.0900 allow local users to gain privileges via a Trojan horse (1) eclipse_1114.dll or (2) emser645mi.dll file in the current working directory, as demonstrated by a directory that contains a .odm, .odt, .otp, .stc, .stw, .sxg, or .sxw file. NOTE: some of these details are obtained from third party information.
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 confidenceIBM Lotus Symphony 1.3.0 contains untrusted search path vulnerabilities where the application loads DLL files (eclipse_1114.dll or emser645mi.dll) from the current working directory instead of secure system paths. An attacker can place a malicious DLL in a directory containing document files (.odm, .odt, .otp, .stc, .stw, .sxg, .sxw) and achieve code execution with the privileges of the user who opens those documents.
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= 1.3.0.20090908.0900CVSS 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
- Local
- Complexity
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed IBM Lotus Symphony versionVerify the installed version of IBM Lotus Symphony on the system (typically via Add/Remove Programs, program directory properties, or the application's About/Help menu)Affected if Version matches 1.3.0.20090908.0900 exactly
-
Locate vulnerable DLL filesSearch the IBM Lotus Symphony installation directory for the presence of eclipse_1114.dll and emser645mi.dllAffected if Either eclipse_1114.dll or emser645mi.dll exists in the application directory
-
Confirm document file type associationVerify that IBM Lotus Symphony is associated with or can open document types .odm, .odt, .otp, .stc, .stw, .sxg, or .sxwAffected if These document file types are associated with the application and can be opened directly
-
Assess typical user document locationsIdentify directories where users commonly store or open the affected document types, particularly shared or download foldersAffected if Users open documents from directories where an attacker could place a malicious DLL
-
Verify DLL search path behaviorCheck if the application loads DLLs from the current working directory by examining Windows DLL search path settings or testing the application's DLL loading behaviorAffected if The current working directory is included in the DLL search path when opening documents
A user is affected if IBM Lotus Symphony version 1.3.0.20090908.0900 is installed and users open the vulnerable document types from directories where a malicious eclipse_1114.dll or emser645mi.dll could be placed.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to a patched version of IBM Lotus Symphony if available, or implement workarounds such as ensuring the application is launched from a trusted directory and preventing user-controlled directories from being added to the DLL search path.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-5204 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2010-5204 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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