CVE-2017-8865
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedElemental Path's CogniToys Dino smart toys through firmware version 0.0.794 do not provide sufficient protections against capture-replay attacks, allowing an attacker on the network to replay VoIP traffic between a Dino device and remote server to any other Dino device.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe CogniToys Dino smart toys through firmware 0.0.794 lack protections against capture-replay attacks on VoIP traffic. An attacker on the same network can intercept and record VoIP communications between a Dino device and the remote server, then replay that traffic to inject audio or commands into other Dino devices.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 0.0.794CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelLocate the physical CogniToys Dino or Stemosaur device and confirm its model name. Check the original packaging, device label, or companion mobile app for model identification.Affected if The device is a CogniToys Dino smart toy or Stemosaur model.
-
Access firmware version informationOpen the CogniToys companion mobile app, navigate to device settings or About section, and look for firmware or software version information. Alternatively, check any device management interface provided by the toy.Affected if Unable to retrieve firmware version from device settings or companion app.
-
Compare firmware version to affected rangeIf firmware version is found, compare it numerically to 0.0.794. Versions 0.0.794 and below are affected; versions above 0.0.794 are not.Affected if Firmware version is 0.0.794 or lower (e.g., 0.0.793, 0.0.700, etc.).
-
Confirm VoIP feature is in useMonitor network traffic from the device using a network sniffer on the same LAN. Look for RTP (Real-time Transport Protocol) or SIP (Session Initiation Protocol) traffic patterns typical of VoIP communications between the device and remote servers.Affected if The device transmits VoIP (RTP/SIP) traffic and firmware version is 0.0.794 or lower.
-
Check for session protections in VoIP trafficCapture a sample of VoIP packets between the Dino device and server. Inspect packet headers for nonces, timestamps, or session tokens that would prevent replay. Absent these, each packet can be replayed.Affected if VoIP packets lack cryptographic protections (nonces, timestamps, session tokens) and firmware version is 0.0.794 or lower.
A user is affected if they have a CogniToys Dino or Stemosaur device running firmware version 0.0.794 or lower that uses VoIP communication without session protection mechanisms.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement cryptographic session protections including nonces, timestamps, and session-specific tokens in the VoIP protocol to ensure each message is unique and cannot be replayed. Update firmware on all deployed devices and ensure server-side validation rejects duplicated or stale packets.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-8865 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-8865 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data