# CVE-2005-0070: Information disclosure in n/a

> Local attackers can read arbitrary files via Synaesthesia when it is installed setuid root, due to failure to drop privileges.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 16 Feb 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DSA-681-1, GHSA-jff7-fm48-4mpp

## What is CVE-2005-0070?

CVE-2005-0070 is a high-severity vulnerability in n/a, published on 16 Feb 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Synaesthesia 2.1 and earlier, and possibly other versions, when installed setuid root, does not drop privileges before processing configuration and mixer files, which allows local users to read arbitrary files.

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

It affects 1 product.


Products: Synaesthesia Synaesthesia.

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

Apply the vendor's patch.

## Is CVE-2005-0070 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-0160](https://insights.sbomify.com/CVE-2004-0160/): Path traversal in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-0070 is a high-severity vulnerability in n/a, published on 16 Feb 2005. 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-2005-0070 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-0070/ (Markdown: https://insights.sbomify.com/CVE-2005-0070/index.md)
```

## Sources

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

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