# CVE-2004-0563: Information disclosure in n/a

> Local attackers can read world-readable configuration files to obtain sensitive credentials, requiring a patch to restrict file permissions.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Nov 2004
- **Updated:** 8 Aug 2024
- **Also known as:** DSA-555-1, GHSA-jw44-2hm2-63x7

## What is CVE-2004-0563?

CVE-2004-0563 is a low-severity vulnerability in n/a, published on 19 Nov 2004. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The tspc.conf configuration file in freenet6 before 0.9.6 and before 1.0 on Debian Linux has world readable permissions, which could allow local users to gain sensitive information, such as a username and password.

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

It affects 1 product.


Products: Freenet6 Freenet6.

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

Apply the vendor's patch.

## Is CVE-2004-0563 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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