Security readout for executives and security teams
Plain-English summary
A flaw in Zephyr RTOS memory boundary checking could let a malicious local application bypass protections between user and kernel memory. Business impact depends on device design and exposed syscalls, ranging from device crashes to data exposure or kernel-level compromise.
Executive priority
Treat this as high priority for Zephyr-based embedded products because impact can reach kernel memory compromise. Urgency is highest where devices run third-party or semi-trusted userspace code, protect sensitive data, or are difficult to patch after deployment.
Technical view
CVE-2020-10067 is an integer overflow in Zephyr's is_in_region logic used by syscall handlers. The overflow can bypass address-range validation, allowing a user thread to access kernel memory. The reported impact includes denial of service, information leak, memory corruption, and possible kernel code execution.
Likely exposure
Exposure is most likely in products built on Zephyr RTOS versions identified in the source bundle, especially devices that run userspace applications and expose vulnerable syscall paths. Confirm exact fixed ranges with Zephyr guidance.
Exploitation context
The CVSS vector indicates local access, low privileges, high attack complexity, and required user interaction. The source bundle does not identify active exploitation, and CISA KEV status is false.
Researcher notes
Evidence supports an integer overflow in syscall memory-region validation. The bundle names Zephyr 1.14.1 and 2.1.0 and describes later versions as affected, but exact fixed release ranges are not provided here. Avoid assuming exploit availability.
Mitigation direction
- Review Zephyr security guidance for CVE-2020-10067 and fixed version details.
- Upgrade affected Zephyr-based firmware to a vendor-supported fixed release or patched branch.
- Review referenced Zephyr pull requests if maintaining a downstream fork.
- Limit deployment of untrusted userspace applications on affected devices.
- Prioritize firmware updates for devices handling sensitive data or safety-critical operations.
Validation and detection
- Inventory products and firmware using Zephyr RTOS.
- Map each firmware build to its Zephyr base version and downstream patches.
- Check whether the referenced Zephyr fixes are present in source or vendor firmware.
- Identify enabled userspace and syscall features in affected builds.
- Document affected device models, firmware versions, and update status.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-190: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2020-10067 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H0.86Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://zephyrprojectsec.atlassian.net/browse/ZEPSEC-27CVE reference · x_refsource_MISC
- https://github.com/zephyrproject-rtos/zephyr/pull/23239CVE reference · x_refsource_MISC
- https://github.com/zephyrproject-rtos/zephyr/pull/23653CVE reference · x_refsource_MISC
- https://github.com/zephyrproject-rtos/zephyr/pull/23654CVE reference · x_refsource_MISC
- https://docs.zephyrproject.org/latest/security/vulnerabilities.html#cve-2020-10067CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Integer Overflow or Wraparound
Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.