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

> Local users can access sensitive chat logs from other users due to shared log file handling in Yahoo! Messenger.

- **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:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 May 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-m522-474x-8pgf

## What is CVE-2005-1671?

CVE-2005-1671 is a low-severity vulnerability in n/a, published on 19 May 2005. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The Logfile feature in Yahoo! Messenger 5.x through 6.0 can be activated by a YMSGR: URL and writes all output to a single ypager.log file, even when there are multiple users, and does not properly warn later users that the feature has been enabled, which allows local users to obtain sensitive information from other users.

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

It affects 1 product.


Products: Yahoo Messenger.

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

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

## Is CVE-2005-1671 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-7216](https://insights.sbomify.com/CVE-2014-7216/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-4515](https://insights.sbomify.com/CVE-2007-4515/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-4391](https://insights.sbomify.com/CVE-2007-4391/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-3147](https://insights.sbomify.com/CVE-2007-3147/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-3148](https://insights.sbomify.com/CVE-2007-3148/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-1671 is a low-severity vulnerability in n/a, published on 19 May 2005. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2005-1671 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-1671/ (Markdown: https://insights.sbomify.com/CVE-2005-1671/index.md)
```

## Sources

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

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