CVE-2012-1896 json
Microsoft .NET Framework 2.0 SP2 and 3.5.1 does not properly consider trust levels during construction of output data, which allows remote…
published 2012-11-14 13 y ago modified 2026-06-16 4 mo ago also EUVD-2012-1906
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 23.7%
- EPSS 23.7% chance of exploitation in 30 days, percentile 97%
- public exploits
- 0
- none known
Summary
Microsoft .NET Framework 2.0 SP2 and 3.5.1 does not properly consider trust levels during construction of output data, which allows remote attackers to obtain sensitive information via (1) a crafted XAML browser application (aka XBAP) or (2) a crafted .NET Framework application, aka "Code Access Security Info Disclosure Vulnerability."
Exploit prediction
23.67% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2012/ms12-074
vendor-advisory
-
securityfocus.com
/bid/56456
vdb-entry
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A15785
vdb-entry, signature
-
us-cert.gov
/cas/techalerts/TA12-318A.html
third-party-advisory, us-government-resource
-
secunia.com
/advisories/51236
third-party-advisory
-
securitytracker.com
/id?1027753
vdb-entry
Sources
- CVE List CVE-2012-1896
- NVD CVE-2012-1896
Fencer Intel 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.