CVE-2008-5100
The strong name (SN) implementation in Microsoft .NET Framework 2.0.50727 relies on the digital...
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.
Exploit likelihood
What each source reports
NVD Score used
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.
- Record
CVE-2008-5100- CVSS 2.0
- 10.0 High
AV:N/AC:L/Au:N/C:C/I:C/A:C - Weakness
- CWE-310
- Updated
- 2026-11-02
CVE ListNo score
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.
- Record
CVE-2008-5100- Updated
- 2026-11-02
EUVDEUVD-2008-5079No score
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.
- Record
EUVD-2008-5079- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-2m57-rxhp-5h39No score
The strong name (SN) implementation in Microsoft .NET Framework 2.0.50727 relies on the digital...
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.
- Record
GHSA-2m57-rxhp-5h39- Updated
- 2026-11-02
Affected products
History
| Recorded | Changed | Sources |
|---|---|---|
| facts | ||
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2008-5100 is a high vulnerability (CVSS 10.0) in Microsoft .net Framework, published November 17, 2008. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 8.37%, the 95th percentile. No source names a fixed version.
References
securityfocus.com/archive/1/498311/100/0/threaded
applicationsecurity.co.il/.NET-Framework-Rootkits.aspx
securityreason.com/securityalert/4605
nvd.nist.gov/vuln/detail/CVE-2008-5100
github.com/advisories/GHSA-2m57-rxhp-5h39