# CVE-2018-8269: Denial of service in ASP.NET Core

> An attacker can cause a denial of service by sending improperly handled web requests to applications using the Microsoft OData library.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mv2r-q4g5-j8q5

## What is CVE-2018-8269?

CVE-2018-8269 is a high-severity denial of service vulnerability in Microsoft.Data.OData, published on 13 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A denial of service vulnerability exists when OData Library improperly handles web requests, aka "OData Denial of Service Vulnerability." This affects Microsoft.Data.OData.

## Which versions are affected by CVE-2018-8269?

10 open source packages ship an affected version, including Microsoft.Data.OData, Microsoft.AspNetCore.All and Microsoft.AspNetCore.DataProtection.AzureStorage. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Microsoft.Data.OData` | NuGet | All versions | 5.8.4 |
| `Microsoft.Data.OData` | NuGet | All versions | 5.8.4 |
| `Microsoft.AspNetCore.All` | NuGet | From 2.1.0 | 2.1.13 |
| `Microsoft.AspNetCore.All` | NuGet | From 2.1.0 | 2.1.13 |
| `Microsoft.AspNetCore.All` | NuGet | From 2.2.0 | 2.2.7 |
| `Microsoft.AspNetCore.All` | NuGet | From 2.2.0 | 2.2.7 |
| `Microsoft.AspNetCore.DataProtection.AzureStorage` | NuGet | From 2.1.0 | 2.1.13 |
| `Microsoft.AspNetCore.DataProtection.AzureStorage` | NuGet | From 2.1.0 | 2.1.13 |
| `Microsoft.AspNetCore.DataProtection.AzureStorage` | NuGet | From 2.2.0 | 2.2.7 |
| `Microsoft.AspNetCore.DataProtection.AzureStorage` | NuGet | From 2.2.0 | 2.2.7 |

Products: Microsoft Microsoft.data.odata.

## How do I fix CVE-2018-8269?

Upgrade Microsoft.Data.OData to 5.8.4 or later.

## Is CVE-2018-8269 being exploited?

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

Public exploit code:

- Microsoft Office SharePoint Server 2016 - Denial of Service (Metasploit) (exploitdb)
- Microsoft Office SharePoint Server 2016 - Denial of Service (Metasploit) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-8269 and fix it if it is affected.

What it is: CVE-2018-8269 is a high-severity denial of service vulnerability in Microsoft.Data.OData, published on 13 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-8269 in the wild and no public exploit code.

Affected packages and fixed versions:
- Microsoft.Data.OData (NuGet): affected all versions; fixed in 5.8.4
- Microsoft.Data.OData (NuGet): affected all versions; fixed in 5.8.4
- Microsoft.AspNetCore.All (NuGet): affected from 2.1.0; fixed in 2.1.13
- Microsoft.AspNetCore.All (NuGet): affected from 2.1.0; fixed in 2.1.13
- Microsoft.AspNetCore.All (NuGet): affected from 2.2.0; fixed in 2.2.7
- Microsoft.AspNetCore.All (NuGet): affected from 2.2.0; fixed in 2.2.7
- Microsoft.AspNetCore.DataProtection.AzureStorage (NuGet): affected from 2.1.0; fixed in 2.1.13
- Microsoft.AspNetCore.DataProtection.AzureStorage (NuGet): affected from 2.1.0; fixed in 2.1.13
- Microsoft.AspNetCore.DataProtection.AzureStorage (NuGet): affected from 2.2.0; fixed in 2.2.7
- Microsoft.AspNetCore.DataProtection.AzureStorage (NuGet): affected from 2.2.0; fixed in 2.2.7

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

## Sources

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

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