CVE-2008-5100
The strong name (SN) implementation in Microsoft .NET Framework 2.0.50727 relies on the digital signature Public Key Token embedded in the pathname of a DLL file instead of the digital signature of this file itself, which makes it easier for attackers…
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (8.37%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
The strong name (SN) implementation in Microsoft .NET Framework 2.0.50727 relies on the digital signature Public Key Token embedded in the pathname of a DLL file instead of the digital signature of this file itself, which makes it easier for attackers to bypass Global Assembly Cache (GAC) and Code Access Security (CAS) protection mechanisms, aka MSRC ticket MSRC8566gs.
- CVSS 2.0
- 10.0 HIGHAV:N/AC:L/Au:N/C:C/I:C/A:C
- EPSS
- 8.37% probability · 95th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-310
- Affected
- microsoft/.net framework
- Source
- cve@mitre.org
References
- http://securityreason.com/securityalert/4605
- http://www.applicationsecurity.co.il/.NET-Framework-Rootkits.aspx
- http://www.applicationsecurity.co.il/LinkClick.aspx?fileticket=ycIS1bewMBI%3d&tabid=161&mid=555Exploit
- http://www.securityfocus.com/archive/1/498311/100/0/threaded
- http://securityreason.com/securityalert/4605
- http://www.applicationsecurity.co.il/.NET-Framework-Rootkits.aspx
- http://www.applicationsecurity.co.il/LinkClick.aspx?fileticket=ycIS1bewMBI%3d&tabid=161&mid=555Exploit
- http://www.securityfocus.com/archive/1/498311/100/0/threaded
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.