dbcve.org
ZephyrOperating system · Zephyrproject

CVE-2020-10064

CRITICAL · 9.8 CVSS v3.1 Published 2021-05-25
Fix available
A fix is available. Upgrade to after 2.2.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Improper Input Frame Validation in ieee802154 Processing. Zephyr versions >= v1.14.2, >= v2.2.0 contain Stack-based Buffer Overflow (CWE-121), Heap-based Buffer Overflow (CWE-122). For more information, see https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-3gvq-h42f-v3c7

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

Buffer overflow vulnerability in Zephyr RTOS IEEE 802.15.4 network stack processing. Improper input validation when parsing ieee802154 frames allows overflow of both stack-based and heap-based buffers. Remotely exploitable with CVSS 9.8, enabling potential code execution or denial of service.

MitigationUpgrade Zephyr to version containing the security patch (refer to GHSA-3gvq-h42f-v3c7). If immediate upgrade is not feasible, restrict network exposure and disable ieee802154 functionality on affected devices until patching can be completed.

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
ZephyrOperating system
Affected:<= 1.14.2>= 2.0.0, <= 2.2.0

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 Zephyr version in use
    Check the Zephyr version header (typically in zephyr/version.h) or inspect build artifacts for version information. The version may also appear in build logs or a version.cmake file.
    Affected if Version is 1.14.2 or earlier, OR between 2.0.0 and 2.2.0 inclusive
  2. Verify ieee802154 module is enabled
    Inspect the Zephyr build configuration (defconfig, prj.conf, or .config) for CONFIG_IEEE802154=y or CONFIG_IEEE802154=m. This configuration option enables the IEEE 802.15.4 network stack.
    Affected if CONFIG_IEEE802154 is set to y or m (enabled as module or built-in)
  3. Check for ieee802154 driver configuration
    Look for ieee802154-specific driver options in the build configuration, such as CONFIG_IEEE802154_NRF5, CONFIG_IEEE802154_CC2520, or other radio driver settings that indicate active IEEE 802.15.4 hardware support.
    Affected if Any ieee802154 radio driver is enabled in the build configuration

A device is affected if it runs a Zephyr version in the ranges <=1.14.2 or 2.0.0-2.2.0 AND has IEEE 802.15.4 networking functionality enabled in the configuration.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 2.2.0
Interim mitigation

Upgrade Zephyr to version containing the security patch (refer to GHSA-3gvq-h42f-v3c7). If immediate upgrade is not feasible, restrict network exposure and disable ieee802154 functionality on affected devices until patching can be completed.

Recommended fix High confidence

Zephyr v2.3.0 or later (or v1.14.3+ if remaining on 1.x branch)

  1. 1. Identify the current Zephyr version in use by checking the manifest file (typically west.yml or zephyr-sdk)
  2. 2. For Zephyr 2.x users: Upgrade to Zephyr v2.3.0 or later stable release which contains the fix for this buffer overflow vulnerability
  3. 3. For Zephyr 1.x users: Upgrade to a version newer than v1.14.2 (e.g., v1.14.3 or later if available, or migrate to 2.x)
  4. 4. Rebuild and redeploy the firmware with the updated Zephyr version
  5. 5. Verify the ieee802154 stack functions correctly after the upgrade
Caveat Potential API changes may exist between Zephyr 2.2.0 and 2.3.0; review the release notes for any breaking changes related to ieee802154 or networking subsystems

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Zephyr Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-10064 — 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-2020-10064 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