# CVE-2006-6085: Information disclosure in n/a

> Local attackers can read sensitive data from Kile backup files due to incorrect permission settings.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/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:** 24 Nov 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-6085, GHSA-x68c-22h5-cx6j

## What is CVE-2006-6085?

CVE-2006-6085 is a medium-severity vulnerability in n/a, published on 24 Nov 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Kile before 1.9.3 does not assign a backup file the same permissions as the original file, which might allow local users to obtain sensitive information.

## Which versions are affected by CVE-2006-6085?

It affects 1 product.


Products: Kile Kile.

## How do I fix CVE-2006-6085?

Upgrade to a fixed version.

## Is CVE-2006-6085 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-6085 and fix it if it is affected.

What it is: CVE-2006-6085 is a medium-severity vulnerability in n/a, published on 24 Nov 2006. 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-2006-6085 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-2006-6085/ (Markdown: https://insights.sbomify.com/CVE-2006-6085/index.md)
```

## Sources

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

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