CVE-2011-0105 in the critical feed json
Microsoft Excel 2002 SP3, Office 2004 and 2008 for Mac, and Open XML File Format Converter for Mac obtain a certain length value from an un…
published 2011-04-13 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-0131
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 70.2%
- EPSS 70.2% chance of exploitation in 30 days, percentile 99.3%
- public exploits
- 2
- Metasploit, Exploit-DB
Summary
Microsoft Excel 2002 SP3, Office 2004 and 2008 for Mac, and Open XML File Format Converter for Mac obtain a certain length value from an uninitialized memory location, which allows remote attackers to trigger a buffer overflow and execute arbitrary code via a crafted Excel file, aka "Excel Data Initialization Vulnerability."
Timeline
- Published
- First public exploit (Metasploit exploit/windows/fileformat/ms11_021_xlb_bof)
Exploit prediction
70.17% chance of exploitation in the next 30 days, higher than 99.3% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit exploit/windows/fileformat/ms11_021_xlb_bof MS11-021 Microsoft Office 2007 Excel .xlb Buffer Overflow metasploit exploit, normal rank, 2011-08-09
- EDB-18087 Microsoft Excel 2007 - '.xlb' Local Buffer Overflow (MS11-021) (Metasploit) local, 2011-11-05
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-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2011/ms11-021
vendor-advisory
-
us-cert.gov
/cas/techalerts/TA11-102A.html
third-party-advisory, us-government-resource
-
secunia.com
/advisories/39122
third-party-advisory
-
securitytracker.com
/id?1025337
vdb-entry
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A12618
vdb-entry, signature
-
vupen.com
/english/advisories/2011/0940
vdb-entry
Sources
- CVE List CVE-2011-0105
- NVD CVE-2011-0105
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.