CVE-2011-0092 in the critical feed json
The LZW stream decompression functionality in ORMELEMS.DLL in Microsoft Visio 2002 SP2, 2003 SP3, and 2007 SP2 allows remote attackers to e…
published 15y ago modified 4mo ago also EUVD-2011-0118
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 24.2%
- EPSS 24.2% chance of exploitation in 30 days, percentile 97%
- public exploits
- 0
- none known
Summary
The LZW stream decompression functionality in ORMELEMS.DLL in Microsoft Visio 2002 SP2, 2003 SP3, and 2007 SP2 allows remote attackers to execute arbitrary code via a Visio file with a malformed VisioDocument stream that triggers an exception handler that accesses an object that has not been fully initialized, which triggers memory corruption, aka "Visio Object Memory Corruption Vulnerability."
Is CVE-2011-0092 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
24.23% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
References
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2011/ms11-008
vendor-advisory
-
vupen.com
/english/advisories/2011/0321
vdb-entry, vendor-advisory
-
secunia.com
/advisories/43254
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/64923
vdb-entry
-
securityfocus.com
/archive/1/516274/100/0/threaded
mailing-list
-
securityfocus.com
/bid/46137
vdb-entry
-
securitytracker.com
/id?1025043
vdb-entry
-
osvdb.org
/70828
vdb-entry
- zerodayinitiative.com /advisories/ZDI-11-063/
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A12403
vdb-entry, signature
Sources
- CVE List CVE-2011-0092
- NVD CVE-2011-0092
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.