# CVE-2017-1000249: Memory corruption in n/a

> A stack buffer overflow in the file() function allows attackers to execute arbitrary code or cause denial of service via a crafted ELF binary.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Sep 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-1000249, DSA-3965-1, GHSA-7wwh-xwjg-8qfp

## What is CVE-2017-1000249?

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

### Official description

An issue in file() was introduced in commit 9611f31313a93aa036389c5f3b15eea53510d4d1 (Oct 2016) lets an attacker overwrite a fixed 20 bytes stack buffer with a specially crafted .notes section in an ELF binary. This was fixed in commit 35c94dc6acc418f1ad7f6241a6680e5327495793 (Aug 2017).

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

## Which versions are affected by CVE-2017-1000249?

It affects 1 product.


Products: File Project File.

## How do I fix CVE-2017-1000249?

Apply the vendor's patch.

## Is CVE-2017-1000249 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-9652](https://insights.sbomify.com/CVE-2014-9652/): Memory corruption in n/a (medium 5.0)
- [CVE-2014-9620](https://insights.sbomify.com/CVE-2014-9620/): Denial of service in n/a (medium 5.0)
- [CVE-2014-9621](https://insights.sbomify.com/CVE-2014-9621/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-1000249 and fix it if it is affected.

What it is: CVE-2017-1000249 is a medium-severity memory corruption vulnerability in n/a, published on 11 Sep 2017. 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-2017-1000249 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-2017-1000249/ (Markdown: https://insights.sbomify.com/CVE-2017-1000249/index.md)
```

## Sources

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

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