# CVE-2005-3341: DHIS tools DNS package (dhis-tools-dns) before 5.0 allows local users to overwrite arbitrary files via a symlink attack on temporary files c


- **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:** 27 Dec 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-3341, DSA-928-1, GHSA-f2hh-4vrx-q5cr

## What is CVE-2005-3341?

CVE-2005-3341 is a low-severity vulnerability in n/a, published on 27 Dec 2005. 

### Official description

DHIS tools DNS package (dhis-tools-dns) before 5.0 allows local users to overwrite arbitrary files via a symlink attack on temporary files created by (1) register-q.sh and (2) register-p.sh.

## Which versions are affected by CVE-2005-3341?

It affects 1 product.


Products: Dhis Tools Dns Package.

## How do I fix CVE-2005-3341?

Upgrade to a fixed version.

## Is CVE-2005-3341 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-3341 and fix it if it is affected.

What it is: CVE-2005-3341 is a low-severity vulnerability in n/a, published on 27 Dec 2005. 
Exploitation: There is no known exploitation of CVE-2005-3341 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-2005-3341/ (Markdown: https://insights.sbomify.com/CVE-2005-3341/index.md)
```

## Sources

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

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