# CVE-2018-3947: Information disclosure in Yi Technology

> An attacker can sniff network traffic to disclose information from Yi Home Camera phone-to-camera communications.

- **Severity:** Critical 9.0 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Nov 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-p6vg-q7p3-vh4v

## What is CVE-2018-3947?

CVE-2018-3947 is a critical vulnerability in Yi Technology, published on 1 Nov 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An exploitable information disclosure vulnerability exists in the phone-to-camera communications of Yi Home Camera 27US 1.8.7.0D. An attacker can sniff network traffic to exploit this vulnerability.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2018-3947?

It affects 2 products.


Products: Yitechnology Yi Home, Yitechnology Yi Home Camera Firmware.

## How do I fix CVE-2018-3947?

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

## Is CVE-2018-3947 being exploited?

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

## Other vulnerabilities in Yi Technology

- [CVE-2018-3900](https://insights.sbomify.com/CVE-2018-3900/): Memory corruption in Yi Technology (critical 9.1)
- [CVE-2018-3910](https://insights.sbomify.com/CVE-2018-3910/): Command injection in Yi Technology (high 8.8)
- [CVE-2018-3935](https://insights.sbomify.com/CVE-2018-3935/): Denial of service in Yi Technology (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-3947 and fix it if it is affected.

What it is: CVE-2018-3947 is a critical vulnerability in Yi Technology, published on 1 Nov 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-3947 in the wild and no public exploit code.

Affected product: Yi Technology. 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-2018-3947/ (Markdown: https://insights.sbomify.com/CVE-2018-3947/index.md)
```

## Sources

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

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