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

> Heap-based buffer overflow in GNU findutils allows arbitrary code execution via a malicious locate database file.

- **Severity:** Medium 6.0 (`AV:N/AC:M/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Jun 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-2452, GHSA-4cfr-8c5p-5jg6, openSUSE-SU-2024:10758-1

## What is CVE-2007-2452?

CVE-2007-2452 is a medium-severity memory corruption vulnerability in n/a, published on 4 Jun 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Heap-based buffer overflow in the visit_old_format function in locate/locate.c in locate in GNU findutils before 4.2.31 might allow context-dependent attackers to execute arbitrary code via a long pathname in a locate database that has the old format, a different vulnerability than CVE-2001-1036.

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `findutils` | openSUSE:Tumbleweed | All versions | 4.8.0-2.15 |

Products: Gnu Findutils.

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

Upgrade to a fixed version.

## Is CVE-2007-2452 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2001-1036](https://insights.sbomify.com/CVE-2001-1036/): Memory corruption in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-2452 is a medium-severity memory corruption vulnerability in n/a, published on 4 Jun 2007. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-2452 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-2007-2452/ (Markdown: https://insights.sbomify.com/CVE-2007-2452/index.md)
```

## Sources

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

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