# CVE-2004-1305: Denial of service in n/a

> Remote attackers can cause a denial of service in Windows via malicious animated cursor files, requiring user interaction to view the content.

- **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:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Jan 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-7cxg-jhh6-g9jr

## What is CVE-2004-1305?

CVE-2004-1305 is a medium-severity denial of service vulnerability in Microsoft Windows 2000, published on 6 Jan 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Windows Animated Cursor (ANI) capability in Windows NT, Windows 2000 through SP4, Windows XP through SP1, and Windows 2003 allow remote attackers to cause a denial of service via (1) the frame number set to zero, which causes an invalid memory address to be used and leads to a kernel crash, or (2) the rate number set to zero, which leads to resource exhaustion and hang.

## Which versions are affected by CVE-2004-1305?

It affects 19 products.


Products: Microsoft Windows 2000, Microsoft Windows 2003 Server, Microsoft Windows 98, Microsoft Windows 98se, Microsoft Windows Me, Microsoft Windows Nt, Microsoft Windows Xp, Nortel Ip Softphone 2050, Nortel Media Communication Server 5100, Nortel Media Communication Server 5200, Nortel Media Processing Server, Nortel Periphonics, Nortel Symposium Agent, Nortel Symposium Call Center Server, Nortel Symposium Express Call Center, Nortel Symposium Network Control Center, Nortel Symposium Tapi Service Provider, Nortel Symposium Web Centre Portal, Nortel Symposium Web Client.

## How do I fix CVE-2004-1305?

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

## Is CVE-2004-1305 being exploited?

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

Public exploit code:

- Microsoft Windows Kernel - '.ANI' File Parsing Crash (exploitdb)

## Other vulnerabilities in Microsoft Windows 2000

- [CVE-2008-4250](https://insights.sbomify.com/CVE-2008-4250/): Microsoft Windows Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2010-0232](https://insights.sbomify.com/CVE-2010-0232/): Microsoft Windows Kernel Exception Handler (high 7.8, exploited in the wild)
- [CVE-2009-1123](https://insights.sbomify.com/CVE-2009-1123/): Microsoft Windows Improper Input Validation (high 7.8, exploited in the wild)
- [CVE-2002-0367](https://insights.sbomify.com/CVE-2002-0367/): Microsoft Windows Privilege Escalation (high 7.8, exploited in the wild)
- [CVE-2010-0269](https://insights.sbomify.com/CVE-2010-0269/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-1305 and fix it if it is affected.

What it is: CVE-2004-1305 is a medium-severity denial of service vulnerability in Microsoft Windows 2000, published on 6 Jan 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-1305 exists.

Affected product: Microsoft Windows 2000. 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-2004-1305/ (Markdown: https://insights.sbomify.com/CVE-2004-1305/index.md)
```

## Sources

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

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