CVE-2009-2495: The Active Template Library (ATL) in Microsoft Visual Studio .NET 2003 SP1, Visual Studio 2005 SP1 and 2008...
The Active Template Library (ATL) in Microsoft Visual Studio .NET 2003 SP1, Visual Studio 2005 SP1 and 2008 Gold and SP1, and Visual C++ 2005 SP1 and 2008 Gold and SP1 does not properly enforce string termination, which allows remote attackers to obtain sensitive information via a crafted HTML document with an ATL (1) component or (2) control that triggers a buffer over-read, related to ATL headers and buffer allocation, aka "ATL Null String Vulnerability."
Security readout for executives and security teams
This is an old Microsoft ATL flaw where certain browser-loaded components can disclose sensitive memory because strings may not be properly terminated. An attacker would need a user to open crafted HTML that invokes an affected ATL component or control. The business risk is mainly legacy software exposure and confidentiality loss, not system takeover based on the provided CVSS vector. Exposure is most likely in legacy Windows environments using ATL components, ActiveX controls, or products built with affected Microsoft ATL headers. The source bundle lists Microsoft development tools and downstream vendor advisories, but does not provide a complete affected product inventory. Handle as a moderate legacy-risk cleanup item unless exposed business workflows still depend on affected browser controls. Prioritize patch verification on older Windows endpoints and vendor applications because the main impact is sensitive information disclosure after user interaction. Mitigation focus: Apply applicable Microsoft updates from MS09-035 and MS09-060 guidance.; Check downstream vendor advisories for affected third-party products.; Prioritize legacy systems that still allow ATL or ActiveX browser components..
Prepared
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · low confidence lookup
CWE-126: 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.
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.
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-126 · source CWE mapping
Buffer Over-read
Buffer Over-read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.