Microsoft .NET Framework 1.0 SP3, 1.1 SP1, 2.0 SP2, 3.5, 3.5.1, 4, 4.5, and 4.5.1 does not properly determine whether…
No fixed version listed yet.Check the vendor advisory. References ↓
Microsoft .NET Framework (versions 1.0 SP3 through 4.5.1) fails to properly determine whether it is safe to execute a method, a flaw known as the Type Traversal Vulnerability. An attacker can execute arbitrary code remotely by luring a user to a crafted web site or by exploiting a crafted .NET Framework application that exposes a COM server endpoint.
Official description · CVE.org
Microsoft .NET Framework 1.0 SP3, 1.1 SP1, 2.0 SP2, 3.5, 3.5.1, 4, 4.5, and 4.5.1 does not properly determine whether it is safe to execute a method, which allows remote attackers to execute arbitrary code via (1) a crafted web site or (2) a crafted .NET Framework application that exposes a COM server endpoint, aka "Type Traversal Vulnerability."
- Exploited
- Not confirmed
- Reports
- 0
- Tactics
- 0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
Public exploit code (Metasploit) was available 1 day before disclosure.
- Public exploit codeMetasploit1 day before
- Disclosedday 0
What security researchers reported
Not named in any threat report yetAlso mentioned in 4 community threat pulses (AlienVault OTX)
Weaker evidencePulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.
- TrojanDownloader:Win32/Tsunovest.A4 Mar 2025
- CVE -CVE Reference Map for Source MS - Curios RE active candidates CVE version 2006110131 Jan 2025
- Thor Lite Scanner - Cigabuntu (Parrot Version) vs. The Book of Shadows13 Jun 2024
- Thor-Lite Linux 64 (06.11.24) - enriched a bit more but not 'pruned'11 Jun 2024