# CVE-2021-3555: Memory corruption in Indoor 2K Indoor Camera

> A local attacker can exploit a buffer overflow in the RSTP server to achieve remote code execution on Eufy Indoor 2K cameras.

- **Severity:** High 7.6 (`CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 May 2022
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-mg3c-6fqg-8j8h

## What is CVE-2021-3555?

CVE-2021-3555 is a high-severity memory corruption vulnerability in Eufy Indoor 2K Indoor Camera, published on 31 May 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A Buffer Overflow vulnerability in the RSTP server component of Eufy Indoor 2K Indoor Camera allows a local attacker to achieve remote code execution. This issue affects: Eufy Indoor 2K Indoor Camera 2.0.9.3 version and prior versions.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2021-3555?

It affects 2 products.


Products: Eufylife Solo Indoorcam C24 Firmware, Eufylife Solo Indoorcam P24 Firmware.

## How do I fix CVE-2021-3555?

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

## Is CVE-2021-3555 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-3555 and fix it if it is affected.

What it is: CVE-2021-3555 is a high-severity memory corruption vulnerability in Eufy Indoor 2K Indoor Camera, published on 31 May 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-2021-3555 in the wild and no public exploit code.

Affected product: Eufy Indoor 2K Indoor Camera. 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-2021-3555/ (Markdown: https://insights.sbomify.com/CVE-2021-3555/index.md)
```

## Sources

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

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