CVE-2009-1534 in the critical feed json
Buffer overflow in the Office Web Components ActiveX Control in Microsoft Office XP SP3, Office 2000 Web Components SP3, Office XP Web Comp…
published 2009-08-12 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-1530
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 51.6%
- EPSS 51.6% chance of exploitation in 30 days, percentile 98%
- public exploits
- 2
- Metasploit, Exploit-DB
Summary
Buffer overflow in the Office Web Components ActiveX Control in Microsoft Office XP SP3, Office 2000 Web Components SP3, Office XP Web Components SP3, BizTalk Server 2002, and Visual Studio .NET 2003 SP1 allows remote attackers to execute arbitrary code via crafted property values, aka "Office Web Components Buffer Overflow Vulnerability."
Patch / fix
Timeline
- First public exploit (Metasploit exploit/windows/browser/ms09_043_owc_htmlurl)
- Published
Exploit prediction
51.61% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Metasploit exploit/windows/browser/ms09_043_owc_htmlurl Microsoft OWC Spreadsheet HTMLURL Buffer Overflow metasploit exploit, normal rank, 2009-08-11
- EDB-16542 Microsoft OWC Spreadsheet - HTMLURL Buffer Overflow (MS09-043) (Metasploit) remote, 2010-04-30
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
-
securityfocus.com
/bid/35992
vdb-entry, patch
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2009/ms09-043
vendor-advisory
-
osvdb.org
/56916
vdb-entry
-
us-cert.gov
/cas/techalerts/TA09-223A.html
third-party-advisory, us-government-resource
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A6326
vdb-entry, signature
-
securitytracker.com
/id?1022708
vdb-entry
Sources
- CVE List CVE-2009-1534
- NVD CVE-2009-1534
Fencer Vulns 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.