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

> Local attackers can retrieve unencrypted VNC passwords from the application's properties dialog, compromising remote access credentials.

- **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:** 28 Jun 2005
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-24gw-m82p-246p

## What is CVE-2002-1848?

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

### Official description

TightVNC before 1.2.4 running on Windows stores unencrypted passwords in the password text control of the WinVNC Properties dialog, which could allow local users to access passwords.

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

It affects 1 product.


Products: Tightvnc Tightvnc.

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

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

## Is CVE-2002-1848 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-0388](https://insights.sbomify.com/CVE-2009-0388/): Integer overflow in n/a (critical 10.0)
- [CVE-2021-42785](https://insights.sbomify.com/CVE-2021-42785/): Buffer Overflow in tvnviewer.exe via Crafted Packet in TightVNC Viewer 2.8.59 (critical 9.8)
- [CVE-2019-15678](https://insights.sbomify.com/CVE-2019-15678/): Memory corruption in TightVNC (critical 9.8)
- [CVE-2019-15679](https://insights.sbomify.com/CVE-2019-15679/): Memory corruption in TightVNC (critical 9.8)
- [CVE-2019-8287](https://insights.sbomify.com/CVE-2019-8287/): Memory corruption in TightVNC (critical 9.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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