# CVE-2022-45478: Information disclosure in Telepad

> Man-in-the-middle attackers can intercept cleartext data, including keypresses, from Telepad devices due to lack of encryption.

- **Severity:** Medium 5.1 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/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:** 5 Dec 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-xq5c-p875-fv6j

## What is CVE-2022-45478?

CVE-2022-45478 is a medium-severity vulnerability in Telepad, published on 5 Dec 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Telepad allows an attacker (in a man-in-the-middle position between the server and a connected device) to see all data (including keypresses) in cleartext. CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2022-45478?

It affects 1 product.


Products: Telepad-App Telepad.

## How do I fix CVE-2022-45478?

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

## Is CVE-2022-45478 being exploited?

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

## Other vulnerabilities in Telepad

- [CVE-2022-45477](https://insights.sbomify.com/CVE-2022-45477/): Auth bypass in Telepad (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-45478 and fix it if it is affected.

What it is: CVE-2022-45478 is a medium-severity vulnerability in Telepad, published on 5 Dec 2022. 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-2022-45478 in the wild and no public exploit code.

Affected product: Telepad. 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-2022-45478/ (Markdown: https://insights.sbomify.com/CVE-2022-45478/index.md)
```

## Sources

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

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