# CVE-2003-1092: Memory corruption in n/a

> A memory allocation flaw in the file utility library may allow attackers to cause undefined behavior or crashes.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 10 Mar 2005
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2003-1092, GHSA-m9jv-2cqm-h52c

## What is CVE-2003-1092?

CVE-2003-1092 is a high-severity memory corruption vulnerability in n/a, published on 10 Mar 2005. 

### Official description

Unknown vulnerability in the "Automatic File Content Type Recognition (AFCTR) Tool version of the file package before 3.41, related to "a memory allocation problem," has unknown impact.

## Which versions are affected by CVE-2003-1092?

It affects 1 product.


Products: Christos Zoulas File 1.

## How do I fix CVE-2003-1092?

Upgrade to a fixed version.

## Is CVE-2003-1092 being exploited?

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

Public exploit code:

- File 3.x - Utility Local Memory Allocation (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-1092 and fix it if it is affected.

What it is: CVE-2003-1092 is a high-severity memory corruption vulnerability in n/a, published on 10 Mar 2005. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-1092 exists.

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-2003-1092/ (Markdown: https://insights.sbomify.com/CVE-2003-1092/index.md)
```

## Sources

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

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