Quick answers
- Is CVE-2009-1537 exploited in the wild?
- Yes. CVE-2009-1537 is known to be exploited in the wild, first recorded on 20 May 2026. Treat it as urgent.
- How severe is CVE-2009-1537?
- Critical severity, with a CVSS score of 9.3, published 20 May 2026.
- Which products and versions are affected?
- Microsoft Directx 7.0 through 9.0c; Microsoft Windows Server 2003 SP2; Microsoft Windows XP SP2 and SP3; Microsoft Windows 2000 SP4.
- Is there a fix for CVE-2009-1537?
- A patch was published on 2009-07-14: Formal patch released via MS09-028 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2009-1537 attacked?
- It is attacked over the network, in an operating system.
- Am I affected by CVE-2009-1537?
- Check whether you run Microsoft Directx, Microsoft Windows Server 2003, Microsoft Windows XP or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A NULL byte overwrite vulnerability exists in the QuickTime Movie Parser Filter (quartz.dll) within Microsoft DirectShow, a component of DirectX. The flaw is triggered when the parser processes a maliciously crafted QuickTime (.mov) media file. An attacker can exploit this by hosting the file on a website or sending it via email, requiring the user to open the file or visit a malicious page. Successful exploitation allows for remote code execution with the privileges of the logged-in user. This vulnerability was notably exploited in the wild in 2009 and is addressed in Microsoft Security Bulletin MS09-028.
Affected products
- Microsoft DirectX 7.0 through 9.0c
- Microsoft Windows 2000 SP4
- Microsoft Windows XP SP2 and SP3
- Microsoft Windows Server 2003 SP2
Timeline
- 2009-05-28: advisory: Initial Microsoft Security Advisory 971778 released
- 2009-05-29: disclosed: NVD Published Date
- 2009-05-01: exploited: Exploited in the wild in May 2009
- 2009-07-14: patched: Formal patch released via MS09-028