CVE-2009-0090 in the critical feed json
Microsoft .NET Framework 1.0 SP3, 1.1 SP1, and 2.0 SP1 does not properly validate .NET verifiable code, which allows remote attackers to ob…
published 2009-10-14 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-0099
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 21.0%
- EPSS 21.0% chance of exploitation in 30 days, percentile 97%
- public exploits
- 0
- none known
Summary
Microsoft .NET Framework 1.0 SP3, 1.1 SP1, and 2.0 SP1 does not properly validate .NET verifiable code, which allows remote attackers to obtain unintended access to stack memory, and execute arbitrary code, via (1) a crafted XAML browser application (XBAP), (2) a crafted ASP.NET application, or (3) a crafted .NET Framework application, aka "Microsoft .NET Framework Pointer Verification Vulnerability."
Exploit prediction
20.98% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-08).
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-264 Permissions, Privileges, and Access Controls
References
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2009/ms09-061
vendor-advisory
-
us-cert.gov
/cas/techalerts/TA09-286A.html
third-party-advisory, us-government-resource
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A5716
vdb-entry, signature
Sources
- CVE List CVE-2009-0090
- NVD CVE-2009-0090
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.