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

> Local attackers can read sensitive log files stored in the Program Files directory by Musicmatch media player.

- **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:** No
- **Published:** 18 Apr 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4h2w-3crc-jwhg

## What is CVE-2005-1167?

CVE-2005-1167 is a low-severity vulnerability in n/a, published on 18 Apr 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Musicmatch 10.00.2047 and earlier store log files in the Program Files directory instead of the user profile, which may allow local users to obtain sensitive information.

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

It affects 1 product.


Products: Musicmatch Jukebox.

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

No fix has been published for CVE-2005-1167 yet. Limit exposure of the affected software until one is available.

## Is CVE-2005-1167 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-1186](https://insights.sbomify.com/CVE-2005-1186/): Security feature bypass in n/a (medium 6.8)
- [CVE-2005-1168](https://insights.sbomify.com/CVE-2005-1168/): Path traversal in n/a (medium 5.0)
- [CVE-2005-1185](https://insights.sbomify.com/CVE-2005-1185/): Privilege escalation in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

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

## Sources

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

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