# CVE-2008-5100: Security feature bypass in n/a

> Attackers can bypass GAC and CAS security mechanisms in .NET Framework by exploiting weak strong name validation based on file paths.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Nov 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-2m57-rxhp-5h39

## What is CVE-2008-5100?

CVE-2008-5100 is a critical vulnerability in Microsoft .Net Framework, published on 17 Nov 2008. 

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

Weakness: CWE-310

## Which versions are affected by CVE-2008-5100?

It affects 1 product.


Products: Microsoft .Net Framework.

## How do I fix CVE-2008-5100?

No fix has been published for CVE-2008-5100 yet. Limit exposure of the affected software until one is available.

## Is CVE-2008-5100 being exploited?

There is no known exploitation of CVE-2008-5100 in the wild and no public exploit code.

## Other vulnerabilities in Microsoft .Net Framework

- [CVE-2020-0646](https://insights.sbomify.com/CVE-2020-0646/): Microsoft .NET Framework Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2017-8759](https://insights.sbomify.com/CVE-2017-8759/): Microsoft .NET Framework Remote Code Execution (high 7.8, exploited in the wild)
- [CVE-2015-1671](https://insights.sbomify.com/CVE-2015-1671/): Microsoft Windows Remote Code Execution (high 7.8, exploited in the wild)
- [CVE-2024-29059](https://insights.sbomify.com/CVE-2024-29059/): Microsoft .NET Framework Information Disclosure (high 7.5, exploited in the wild)
- [CVE-2014-4073](https://insights.sbomify.com/CVE-2014-4073/): Privilege escalation in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-5100 and fix it if it is affected.

What it is: CVE-2008-5100 is a critical vulnerability in Microsoft .Net Framework, published on 17 Nov 2008. 
Exploitation: There is no known exploitation of CVE-2008-5100 in the wild and no public exploit code.

Affected product: Microsoft .Net Framework. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2008-5100/ (Markdown: https://insights.sbomify.com/CVE-2008-5100/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2008-5100
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2008-5100
- OSV: https://osv.dev/vulnerability/CVE-2008-5100

---
From sbomify Insights: https://insights.sbomify.com/CVE-2008-5100/
Summaries are generated and may contain mistakes; the official description above is the record.