Skip to content
Fencer Intel
medium 6.4

CVE-2010-3332 json

Microsoft .NET Framework 1.1 SP1, 2.0 SP1 and SP2, 3.5, 3.5 SP1, 3.5.1, and 4.0, as used for ASP.NET in Microsoft Internet Information Serv…

published 16y ago modified 4mo ago also EUVD-2010-3330

cvss
6.4
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
68.2%
EPSS 68.2% chance of exploitation in 30 days, percentile 99.3%
public exploits
3
Exploit-DB

Summary

Microsoft .NET Framework 1.1 SP1, 2.0 SP1 and SP2, 3.5, 3.5 SP1, 3.5.1, and 4.0, as used for ASP.NET in Microsoft Internet Information Services (IIS), provides detailed error codes during decryption attempts, which allows remote attackers to decrypt and modify encrypted View State (aka __VIEWSTATE) form data, and possibly forge cookies or read application files, via a padding oracle attack, aka "ASP.NET Padding Oracle Vulnerability."

Patch / fix

Is CVE-2010-3332 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. Published
  2. First public exploit (EDB-15213)

Exploit prediction

68.23% chance of exploitation in the next 30 days, higher than 99.3% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-15292 Microsoft ASP.NET - Auto-Decryptor File Download (MS10-070) remote, 2010-10-20
  • EDB-15265 Microsoft ASP.NET - Padding Oracle File Download (MS10-070) remote, 2010-10-17
  • EDB-15213 Microsoft ASP.NET - Padding Oracle (MS10-070) remote, 2010-10-06
  • troyhunt.com http://www.troyhunt.com/2010/09/fear-uncertainty-and-and-padding-oracle.html referenced PoC, tagged "exploit" by a source, unverified
  • mono-project.com http://www.mono-project.com/Vulnerabilities#ASP.NET_Padding_Oracle referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 6.4 AV:N/AC:L/Au:N/C:P/I:P/A:N

Classification

Weakness
  • CWE-209 Generation of Error Message Containing Sensitive Information

References

Sources

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.