# CVE-2002-0343: Information disclosure in n/a

> Local attackers can read plaintext passwords from the Hotline Client bookmarks file to gain unauthorized access and privileges.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 3 May 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-r4rm-fp8q-jq3x

## What is CVE-2002-0343?

CVE-2002-0343 is a medium-severity vulnerability in n/a, published on 3 May 2002. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Hotline Client 1.8.5 stores sensitive user information, including passwords, in plaintext in the bookmarks file, which could allow local users with access to the bookmarks file to gain privileges by extracting the passwords.

## Which versions are affected by CVE-2002-0343?

It affects 1 product.


Products: Hotline Communications Hotline Connect.

## How do I fix CVE-2002-0343?

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

## Is CVE-2002-0343 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-0343 and fix it if it is affected.

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

## Sources

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

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