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

> Remote attackers can cause application crashes via long strings in file properties, requiring user interaction to open the malicious file.

- **Severity:** Medium 4.3 (`AV:N/AC:M/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:** 1 Oct 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-6r26-5g48-43w4

## What is CVE-2007-5145?

CVE-2007-5145 is a medium-severity memory corruption vulnerability in Microsoft Windows Xp, published on 1 Oct 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

Multiple buffer overflows in system DLL files in Microsoft Windows XP, as used by Microsoft Windows Explorer (explorer.exe) 6.00.2900.2180, Don Ho Notepad++, unspecified Adobe Macromedia applications, and other programs, allow user-assisted remote attackers to cause a denial of service (application crash) via long strings in the (1) author, (2) title, (3) subject, and (4) comment Properties fields of a file, possibly involving improper handling of extended file attributes by the (a) NtQueryInformationFile, (b) NtQueryDirectoryFile, (c) NtSetInformationFile, (d) FileAllInformation, (e) FileNameInformation, and other FILE_INFORMATION_CLASS functions in ntdll.dll and the (f) GetFileAttributesExW and (g) GetFileAttributesW functions in kernel32.dll, a related issue to CVE-2007-1347.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Microsoft Windows Xp.

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

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

## Is CVE-2007-5145 being exploited?

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

## Other vulnerabilities in Microsoft Windows Xp

- [CVE-2012-1852](https://insights.sbomify.com/CVE-2012-1852/): Memory corruption in n/a (critical 10.0)
- [CVE-2012-1853](https://insights.sbomify.com/CVE-2012-1853/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-0119](https://insights.sbomify.com/CVE-2009-0119/): Memory corruption in n/a (critical 10.0)
- [CVE-2007-1946](https://insights.sbomify.com/CVE-2007-1946/): Integer overflow in n/a (critical 10.0)
- [CVE-2005-3595](https://insights.sbomify.com/CVE-2005-3595/): Hardcoded credentials in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-5145 is a medium-severity memory corruption vulnerability in Microsoft Windows Xp, published on 1 Oct 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: There is no known exploitation of CVE-2007-5145 in the wild and no public exploit code.

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

## Sources

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

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