dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-8414

CRITICAL · 9.4 CVSS v4.0 Published 2025-10-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
Zero-click

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 · unedited
Due to improper input validation, a buffer overflow vulnerability is present in Zigbee EZSP Host Applications. If the buffer overflows, stack corruption is possible. In certain conditions, this could lead to arbitrary code execution. Access to a network key is required to exploit this vulnerability.

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 confidence

A buffer overflow vulnerability in Zigbee EZSP Host Applications stems from improper input validation, allowing stack corruption that could lead to arbitrary code execution. Exploitation requires an attacker to possess a valid network key for the Zigbee network.

MitigationApply patches or updates to the EZSP Host Applications that enforce proper input validation and bounds checking. Additionally, strictly control access to network keys and implement network segmentation to limit exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Adjacent
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if EZSP Host Application is running
    Check for processes or services related to EZSP (EmberZNet Serial Protocol) such as silabs-ezsp, ember-ncp, or Zigbee host controller applications. On Linux, run: ps aux | grep -i ezsp or systemctl list-units | grep -i zigbee
    Affected if No EZSP-related processes found means likely not affected by this specific vulnerability
  2. Determine the EZSP Host Application version
    Query the installed package or application version. Common methods: dpkg -l | grep -i silabs, rpm -qa | grep -i ember, or check the application binary with: <binary_path> --version. Also check /opt/silabs or /usr/share/zigbee for version files
    Affected if Unable to obtain a version number, or version is older than the latest patched version from Silicon Labs
  3. Verify Zigbee network configuration is active
    Check if a Zigbee network interface exists and is active. On Linux: ip link show | grep -i zigbee, or check NetworkManager: nmcli device status. Also inspect config files in /etc/zigbee or /opt/silabs/config for network key presence
    Affected if Zigbee network is active and configured with a network key - the system is potentially exposed
  4. Inspect network key access controls
    Review who has access to the network key. Check file permissions on key storage files (often in /etc/zigbee, /opt/silabs, or application config directories): ls -la <key_file> and review access logs if available
    Affected if Network key is accessible to untrusted users or stored with weak permissions - exploitation becomes feasible for attackers with network access
  5. Confirm the application handles EZSP frames
    Check if the application processes incoming EZSP frames. Review logs for EZSP activity: journalctl -u <zigbee-service> --since '1 hour ago' | grep -i ezsp, or tcpdump for port 9999/TCP if used for EZSP communication
    Affected if Application actively processes EZSP frames from the network - the attack surface is present

A system is affected if it runs a vulnerable version of Zigbee EZSP Host Applications with an active Zigbee network configuration and the application processes EZSP frames, especially if network key access is not strictly controlled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply patches or updates to the EZSP Host Applications that enforce proper input validation and bounds checking. Additionally, strictly control access to network keys and implement network segmentation to limit exposure.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-8414 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-8414 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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