# CVE-2023-36873: .NET Framework Spoofing Vulnerability


- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N/E:P/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 8 Aug 2023
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-xrx4-g976-77rm

## What is CVE-2023-36873?

CVE-2023-36873 is a high-severity vulnerability in Microsoft .Net Framework, published on 8 Aug 2023. 

### Official description

.NET Framework Spoofing Vulnerability

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2023-36873?

It affects 1 product.


Products: Microsoft .Net Framework.

## How do I fix CVE-2023-36873?

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

## Is CVE-2023-36873 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-36873 exists.

## 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-2023-36873 and fix it if it is affected.

What it is: CVE-2023-36873 is a high-severity vulnerability in Microsoft .Net Framework, published on 8 Aug 2023. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-36873 exists.

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-2023-36873/ (Markdown: https://insights.sbomify.com/CVE-2023-36873/index.md)
```

## Sources

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

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