# CVE-2021-37436: Information disclosure in n/a

> Attackers with physical access to a factory-reset Amazon Echo Dot can extract sensitive data via complex hardware and software attacks.

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:P/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:** 24 Jul 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-6gjm-vrf7-xg3w

## What is CVE-2021-37436?

CVE-2021-37436 is a medium-severity vulnerability in n/a, published on 24 Jul 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Amazon Echo Dot devices through 2021-07-02 sometimes allow attackers, who have physical access to a device after a factory reset, to obtain sensitive information via a series of complex hardware and software attacks. NOTE: reportedly, there were vendor marketing statements about safely removing personal content via a factory reset. Also, the vendor has reportedly indicated that they are working on mitigations.

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

It affects 1 product.


Products: Amazon Echo Dot Firmware.

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

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

## Is CVE-2021-37436 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-25809](https://insights.sbomify.com/CVE-2022-25809/): Other in n/a (critical 9.8)
- [CVE-2018-11567](https://insights.sbomify.com/CVE-2018-11567/): Information disclosure in n/a (low 3.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-37436 is a medium-severity vulnerability in n/a, published on 24 Jul 2021. 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-37436 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-2021-37436/ (Markdown: https://insights.sbomify.com/CVE-2021-37436/index.md)
```

## Sources

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

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