# CVE-2005-1665: Denial of service in n/a

> Remote attackers can cause CPU exhaustion and denial of service in ASP.NET applications by sending deeply nested markup if ViewState is not cryptographically signed.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 May 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-jgxg-6xxj-cch8

## What is CVE-2005-1665?

CVE-2005-1665 is a medium-severity denial of service vulnerability in n/a, published on 18 May 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The __VIEWSTATE functionality in Microsoft ASP.NET 1.x, when not cryptographically signed, allows remote attackers to cause a denial of service (CPU consumption) via deeply nested markup.

## Which versions are affected by CVE-2005-1665?

It affects 1 product.


Products: Microsoft Asp.net.

## How do I fix CVE-2005-1665?

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

## Is CVE-2005-1665 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-0847](https://insights.sbomify.com/CVE-2004-0847/): Auth bypass in n/a (critical 9.8)
- [CVE-2006-1364](https://insights.sbomify.com/CVE-2006-1364/): Denial of service in n/a (high 7.5)
- [CVE-2003-0768](https://insights.sbomify.com/CVE-2003-0768/): Security feature bypass in n/a (medium 6.8)
- [CVE-2005-1664](https://insights.sbomify.com/CVE-2005-1664/): Other in n/a (medium 6.4)
- [CVE-2005-2224](https://insights.sbomify.com/CVE-2005-2224/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-1665 and fix it if it is affected.

What it is: CVE-2005-1665 is a medium-severity denial of service vulnerability in n/a, published on 18 May 2005. 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-2005-1665 in the wild and no public exploit code.

Affected product: n/a. 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-2005-1665/ (Markdown: https://insights.sbomify.com/CVE-2005-1665/index.md)
```

## Sources

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

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