# CVE-2017-8867: Weak cryptography in n/a

> Attackers can eavesdrop on children's voice communications due to weak AES-ECB encryption in CogniToys Dino smart toys.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xjg4-r4q3-x4xx

## What is CVE-2017-8867?

CVE-2017-8867 is a medium-severity vulnerability in n/a, published on 11 Dec 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Elemental Path's CogniToys Dino smart toys through firmware version 0.0.794 use AES-128 with ECB mode to encrypt voice traffic between the device and remote server, allowing a malicious user to map encrypted traffic to a particular AES key index and gaining further access to eavesdrop on privacy-sensitive voice communication of a child and their Dino device.

## Which versions are affected by CVE-2017-8867?

It affects 1 product.


Products: Cognitoys Stemosaur Firmware.

## How do I fix CVE-2017-8867?

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

## Is CVE-2017-8867 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-8865](https://insights.sbomify.com/CVE-2017-8865/): Other in n/a (medium 5.9)
- [CVE-2017-8866](https://insights.sbomify.com/CVE-2017-8866/): Hardcoded credentials in n/a (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-8867 and fix it if it is affected.

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

## Sources

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

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