# CVE-2007-1765: Memory corruption in n/a

> Remote attackers can execute arbitrary code or cause denial of service via malformed ANI files processed by Windows cursor handling.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **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:** 30 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-f56g-48jx-gg6q

## What is CVE-2007-1765?

CVE-2007-1765 is a critical memory corruption vulnerability in Microsoft Ie, published on 30 Mar 2007. 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

Unspecified vulnerability in Microsoft Windows 2000 SP4 through Vista allows remote attackers to execute arbitrary code or cause a denial of service (persistent reboot) via a malformed ANI file, which results in memory corruption when processing cursors, animated cursors, and icons, a similar issue to CVE-2005-0416, as originally demonstrated using Internet Explorer 6 and 7.  NOTE: this issue might be a duplicate of CVE-2007-0038; if so, then use CVE-2007-0038 instead of this identifier.

## Which versions are affected by CVE-2007-1765?

It affects 10 products.


Products: Avaya Definity One Media Server, Avaya Ip600 Media Servers, Avaya S3400, Avaya S8100, Microsoft Ie, Microsoft Internet Explorer, Microsoft Windows 2000, Microsoft Windows 2003 Server, Microsoft Windows Vista, Microsoft Windows Xp.

## How do I fix CVE-2007-1765?

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

## Is CVE-2007-1765 being exploited?

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

Public exploit code:

- Windows ANI LoadAniIcon() Chunk Size Stack Buffer Overflow (SMTP) (metasploit)
- Microsoft Windows - Animated Cursor '.ani' Local Stack Overflow (exploitdb)
- Microsoft Windows XP/Vista - Animated Cursor '.ani' Remote Overflow (exploitdb)
- Microsoft Windows XP - Animated Cursor '.ani' Remote Overflow (2) (exploitdb)
- Microsoft Windows - Animated Cursor '.ani' Remote (eeye patch Bypass) (exploitdb)
- Microsoft Windows - Animated Cursor '.ani' Local Buffer Overflow (exploitdb)

## Other vulnerabilities in Microsoft Ie

- [CVE-2004-1050](https://insights.sbomify.com/CVE-2004-1050/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0201](https://insights.sbomify.com/CVE-2004-0201/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0212](https://insights.sbomify.com/CVE-2004-0212/): Memory corruption in n/a (critical 10.0)
- [CVE-2007-2374](https://insights.sbomify.com/CVE-2007-2374/): Code injection in n/a (critical 9.3)
- [CVE-2004-0842](https://insights.sbomify.com/CVE-2004-0842/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-1765 and fix it if it is affected.

What it is: CVE-2007-1765 is a critical memory corruption vulnerability in Microsoft Ie, published on 30 Mar 2007. 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-2007-1765 exists.

Affected product: Microsoft Ie. 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-2007-1765/ (Markdown: https://insights.sbomify.com/CVE-2007-1765/index.md)
```

## Sources

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

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