# CVE-2004-1110: The mtink status monitor before 1.0.5 for Epson printers allows local users to overwrite arbitrary files via a symlink attack on the epson temporary file.


- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 1 Dec 2004
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2004-1110, GHSA-2gj9-rr22-j6qf

## What is CVE-2004-1110?

CVE-2004-1110 is a low-severity vulnerability in Gentoo Linux, published on 1 Dec 2004. 

### Official description

The mtink status monitor before 1.0.5 for Epson printers allows local users to overwrite arbitrary files via a symlink attack on the epson temporary file.

## Which versions are affected by CVE-2004-1110?

It affects 2 products.


Products: Gentoo Linux, Jean-Jacques Sarton Mtink.

## How do I fix CVE-2004-1110?

Upgrade to a fixed version.

## Is CVE-2004-1110 being exploited?

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

## Other vulnerabilities in Gentoo Linux

- [CVE-2004-0914](https://insights.sbomify.com/CVE-2004-0914/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-1037](https://insights.sbomify.com/CVE-2004-1037/): Command injection in n/a (critical 10.0)
- [CVE-2004-1034](https://insights.sbomify.com/CVE-2004-1034/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0891](https://insights.sbomify.com/CVE-2004-0891/): Memory corruption in n/a (critical 10.0)
- [CVE-2002-1337](https://insights.sbomify.com/CVE-2002-1337/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-1110 and fix it if it is affected.

What it is: CVE-2004-1110 is a low-severity vulnerability in Gentoo Linux, published on 1 Dec 2004. 
Exploitation: There is no known exploitation of CVE-2004-1110 in the wild and no public exploit code.

Affected product: Gentoo Linux. 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-2004-1110/ (Markdown: https://insights.sbomify.com/CVE-2004-1110/index.md)
```

## Sources

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

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