CVE-2008-5100

What it is

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.

At a glance

Exploitability

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

Exploit odds

8.4% chance of exploitation in the next 30 days (EPSS).

Fix

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

Timeline

1. 2008-11-17 00:00 UTC ReservedThe CVE id was reserved by its CNA
2. 2008-11-17 18:18 UTC PublishedDisclosed publicly on CVE.org and NVD
3. 2026-06-16 22:59 UTC Last updatedMost recent change to the record

Why it ranks here

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

Details

Published

2008-11-17 18:18 UTC

Last modified

2026-06-16 22:59 UTC

Exploit probability

8.4% · EPSS, next 30 days

Weakness

CWE-310

Record status

Modified

Affected

• Microsoft .net Framework 2.0.50727

Attack profile CVSS 2.0 · 10.0

Attack vector

Network

Complexity

Low

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-2008-5100.md and follow it. Check whether this project is affected by CVE-2008-5100. 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