LiveActive security incident?Get immediate response
CVE Record

CVE-2020-10022: UpdateHub Module Copies a Variable-Size Hash String Into a Fixed-Size Array

A malformed JSON payload that is received from an UpdateHub server may trigger memory corruption in the Zephyr OS. This could result in a denial of service in the best case, or code execution in the worst case. See NCC-NCC-016 This issue affects: zephyrproject-rtos zephyr version 2.1.0 and later versions. version 2.2.0 and later versions.

CriticalCVSS 9Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A malformed JSON response from an UpdateHub server can corrupt memory in Zephyr OS. For businesses shipping Zephyr-based devices, the concern is device crashes or, in the worst case, attacker-controlled code execution. The source bundle does not show active exploitation.

Executive priority

Treat this as high priority for affected connected devices because impact could include outages or code execution. Prioritize externally reachable update paths and products still receiving remote updates.

Technical view

CVE-2020-10022 is a CWE-120 fixed-size buffer copy issue in Zephyr's UpdateHub module. A variable-size hash string from JSON may be copied into a fixed-size array, causing memory corruption. CVSS 3.1 is 9.0 with network attack vector, no privileges, no user interaction, and high complexity.

Likely exposure

Exposure is most likely in embedded products using affected Zephyr versions with UpdateHub functionality enabled or reachable. The bundle names Zephyr 2.1.0 and 2.2.0, while the description also says later versions, so teams should verify exact branches against Zephyr guidance.

Exploitation context

The bundle marks CISA KEV as false and provides no cited evidence of exploitation in the wild. Exploitation would require delivering a malformed JSON payload from an UpdateHub server path, and the CVSS vector rates attack complexity as high.

Researcher notes

Evidence is strong for the vulnerable pattern and impact, but incomplete on exact fixed versions in the prompt. The affected-version wording is inconsistent, so validation should use Zephyr's advisory and referenced PRs rather than assuming only two releases are affected.

Mitigation direction

  • Inventory products and firmware builds using Zephyr and UpdateHub.
  • Check Zephyr advisory ZEPSEC-28 and linked pull requests for fixed versions.
  • Upgrade or backport vendor-confirmed fixes where affected versions are present.
  • Restrict trust and network exposure for UpdateHub server communications.
  • Monitor vendor advisories for version clarification and downstream firmware updates.

Validation and detection

  • Identify Zephyr version and commit in each firmware build.
  • Confirm whether UpdateHub is compiled, configured, or reachable.
  • Compare local UpdateHub code against linked Zephyr pull requests.
  • Review firmware update server trust boundaries and JSON parsing paths.
  • Run regression tests for firmware update flows after remediation.
Prepared
Confidence
medium
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-120: 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 lookup
description · low confidence lookup

Execution 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 lookup
cve · low confidence lookup

CVE-2020-10022 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9 (3.1)
Known Exploited
No
Published

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

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
9CVSS 3.1CriticalCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H2.26Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9Critical
CVSS 3.1 vector shape for CVE-2020-10022Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
zephyrproject-rtoszephyr2.1.0, 2.2.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.