Security readout for executives and security teams
This is an old but serious Microsoft DirectShow flaw. A user on affected legacy Windows systems could trigger remote code execution by opening malicious QuickTime media. The source bundle states it was exploited in the wild in May 2009 and is listed in CISA KEV, so legacy exposure should be treated as urgent. Exposure is most likely on unsupported or poorly isolated Windows 2000, Windows XP, and Windows Server 2003 systems that still process QuickTime media through DirectShow. Modern Windows assets are not named in the supplied affected list. Prioritize any remaining legacy Windows exposure. This is a known-exploited remote code execution issue, but the affected products are old and should be rare in a modern estate. Mitigation focus: Apply Microsoft MS09-028 security updates where the affected platform is still supported.; Retire, replace, or isolate Windows 2000, XP, and Server 2003 assets.; Restrict untrusted QuickTime media handling on affected legacy systems..
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-158: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2009-1537 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- Yes
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CISA KEV status
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- Added to KEVCISA-ADP
CISA Known Exploited Vulnerabilities metadata lists this CVE as known exploited.
- ADP timelineCISA-ADP
CVE-2009-1537 added to CISA KEV
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-05-20T00:00:00.000Z: CVE-2009-1537 added to CISA KEV
Source materials
- CVE List V5 sourceCVE List V5
- MS09-028CVE reference, microsoft · vendor-advisory, x_refsource_MS
- oval:org.mitre.oval:def:6237CVE reference, microsoft · vdb-entry, signature
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2009-1537CVE reference, CISA-ADP · government-resource
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Null Byte or NUL Character
Improper Neutralization of Null Byte or NUL Character represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.