Z\/ip Gateway SdkApplication · Silabs

CVE-2023-0970

MEDIUM · 6.8 CVSS v3.1 Published 2023-06-21
Fix available
A fix is available. Upgrade to after 7.18.01 or later.
See remediation →
73/100
Remediation priority · Elevated
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
Multiple buffer overflow vulnerabilities in SiLabs Z/IP Gateway SDK version 7.18.01 and earlier allow an attacker with invasive physical access to a Z-Wave controller device to overwrite global memory and potentially execute arbitrary code.

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 · moderate confidence

Multiple buffer overflow vulnerabilities exist in SiLabs Z/IP Gateway SDK versions 7.18.01 and earlier. An attacker with invasive physical access to a Z-Wave controller device can exploit these overflows to overwrite global memory and potentially achieve arbitrary code execution.

MitigationApply available firmware updates from SiLabs for affected Z-Wave controllers and implement physical security controls to restrict access to controller hardware.

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
Z\/ip Gateway SdkApplication
Affected:<= 7.18.01

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

CVSS:3.1/AV:P/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 Z/IP Gateway SDK installation
    Search system for files or packages related to Z/IP Gateway, such as ZIPGateway executable, or check installed software listings for SiLabs Z/IP Gateway SDK
    Affected if Z/IP Gateway SDK software is found on the system
  2. Determine installed SDK version
    Run version check on the Z/IP Gateway binary or check product documentation/packaging for version string. Common commands: ZIPGateway --version, or inspect binary metadata
    Affected if Installed version is 7.18.01 or earlier, or version cannot be determined but the software is present
  3. Confirm Z-Wave controller role
    Inspect configuration files or runtime settings to determine if the device or software is operating as a Z-Wave controller (primary or secondary)
    Affected if Device is configured as a Z-Wave controller handling Z-Wave network communications
  4. Assess physical access exposure
    Evaluate whether the Z-Wave controller hardware is accessible to untrusted individuals who could gain invasive physical access
    Affected if Controller hardware is in an unsecured or publicly accessible location

Environment is affected if Z/IP Gateway SDK version 7.18.01 or earlier is installed and the system functions as a Z-Wave controller with potential physical access by untrusted parties

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 7.18.01
Interim mitigation

Apply available firmware updates from SiLabs for affected Z-Wave controllers and implement physical security controls to restrict access to controller hardware.

Recommended fix Moderate confidence

Z/IP Gateway SDK > 7.18.01 (contact Silicon Labs for exact fixed release number)

  1. Check current Z/IP Gateway SDK version in use (typically found in SDK installation directory or project manifest)
  2. Visit siliconlabs.lightning.force.com and search for CVE-2023-0970 or Z/IP Gateway SDK security patches
  3. Download and apply the latest Z/IP Gateway SDK version (ensure version is greater than 7.18.01)
  4. Rebuild and redeploy any custom Z-Wave gateway applications using the updated SDK
  5. Verify the upgrade resolves the vulnerability through release notes or security advisory confirmation
Caveat Check Silicon Labs migration guide for potential API changes or configuration updates required when upgrading

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

Fix this in Z\/ip Gateway Sdk Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-0970 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-0970 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