CVE-2012-0015

What it is

Microsoft .NET Framework 2.0 SP2 and 3.5.1 does not properly calculate the length of an unspecified buffer, which allows remote attackers to execute arbitrary code via (1) a crafted XAML browser application (aka XBAP), (2) a crafted ASP.NET application, or (3) a crafted .NET Framework application, aka ".NET Framework Heap Corruption Vulnerability."

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data exposure, data tampering, service disruption.

Exploit odds

23.5% chance of exploitation in the next 30 days (EPSS). Higher than most.

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2012-02-14 22:55 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-16 23:36 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 23.5% in the next 30 days (EPSS).
• Severity: 9.3 HIGH (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2012-02-14 22:55 UTC

Last modified

2026-06-16 23:36 UTC

Exploit probability

23.5% · EPSS, next 30 days

Weakness

CWE-94 · Code injection

Record status

Modified

Affected

• Microsoft .net Framework 2.0
• Microsoft .net Framework 3.5.1

Attack profile CVSS 2.0 · 9.3

Attack vector

Network

Complexity

Medium

Authentication

None

Confidentiality

Complete

Integrity

Complete

Availability

Complete

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2012-0015.md and follow it. Check whether this project is affected by CVE-2012-0015. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge