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

> A buffer overflow in the inotify-tools library allows attackers to execute arbitrary code via a long filename.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Sep 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-5037, DSA-1440-1, GHSA-gv4p-444g-3cqq

## What is CVE-2007-5037?

CVE-2007-5037 is a medium-severity memory corruption vulnerability in n/a, published on 24 Sep 2007. 

### Official description

Buffer overflow in the inotifytools_snprintf function in src/inotifytools.c in the inotify-tools library before 3.11 allows context-dependent attackers to execute arbitrary code via a long filename.

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

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

It affects 1 product.


Products: Inotify Inotify-Tools.

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

Upgrade to a fixed version.

## Is CVE-2007-5037 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2007-5037 is a medium-severity memory corruption vulnerability in n/a, published on 24 Sep 2007. 
Exploitation: There is no known exploitation of CVE-2007-5037 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-5037/ (Markdown: https://insights.sbomify.com/CVE-2007-5037/index.md)
```

## Sources

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

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