# CVE-2024-35495: Information disclosure in n/a

> Attackers can observe device state by monitoring network traffic from TP-Link Kasa and Tapo smart plugs.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Sep 2024
- **Updated:** 30 Oct 2024
- **Also known as:** GHSA-hrqj-68hr-6cvc

## What is CVE-2024-35495?

CVE-2024-35495 is a medium-severity vulnerability in n/a, published on 30 Sep 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An Information Disclosure vulnerability in the Telemetry component in TP-Link Kasa KP125M V1.0.0 and Tapo P125M 1.0.0 Build 220930 Rel.143947 allows attackers to observe device state via observing network traffic.

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

## Which versions are affected by CVE-2024-35495?


## How do I fix CVE-2024-35495?

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

## Is CVE-2024-35495 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-35495 and fix it if it is affected.

What it is: CVE-2024-35495 is a medium-severity vulnerability in n/a, published on 30 Sep 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-35495 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-2024-35495/ (Markdown: https://insights.sbomify.com/CVE-2024-35495/index.md)
```

## Sources

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

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