dbcve.org
Classic Buffer OverflowWeakness · CWE-120

CVE-2024-22472

HIGH · 8.1 CVSS v3.1 Published 2024-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/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
A buffer Overflow vulnerability in Silicon Labs 500 Series Z-Wave devices may allow Denial of Service, and potential Remote Code execution This issue affects all versions of Silicon Labs 500 Series SDK prior to v6.85.2 running on Silicon Labs 500 series Z-wave devices.

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 exists in the Silicon Labs 500 Series SDK (versions prior to v6.85.2) when running on Silicon Labs 500 series Z-Wave devices. This memory corruption flaw can be exploited to cause Denial of Service and potentially achieve Remote Code Execution on affected devices.

MitigationUpgrade the Silicon Labs 500 Series SDK to version 6.85.2 or later to remediate this vulnerability. Prior to deployment, test the update in a controlled environment to ensure compatibility with specific device implementations.

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

CVSS:3.1/AV:N/AC:H/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 the device model
    Check the device documentation, label, or management interface to confirm it is a Silicon Labs 500 series Z-Wave device. Look for model numbers or product identifiers specific to the 500 series.
    Affected if The device is NOT a Silicon Labs 500 series Z-Wave device - this CVE only applies to that specific product line.
  2. Locate the SDK version information
    Access the device firmware, SDK documentation, or management interface to find the installed Silicon Labs 500 Series SDK version. This may be displayed in system information, firmware details, or within the SDK release notes included with the device.
    Affected if Unable to determine the SDK version - without version information, the vulnerability status cannot be confirmed.
  3. Compare the installed version to the fix version
    Take the identified SDK version and compare it numerically to version 6.85.2. Check if the version is prior to 6.85.2, equal to 6.85.2, or later than 6.85.2.
    Affected if The installed SDK version is lower than 6.85.2 - versions prior to v6.85.2 are vulnerable to the buffer overflow.
  4. Verify the Z-Wave functionality is enabled
    Confirm that the Z-Wave radio or network feature is active on the device, as the vulnerability applies when the device runs Z-Wave operations using the affected SDK.
    Affected if Z-Wave functionality is not enabled or not in use - the vulnerability may not be exploitable in this configuration.

A user is affected if they have a Silicon Labs 500 series Z-Wave device running the SDK version prior to 6.85.2 with Z-Wave features enabled.

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

Upgrade the Silicon Labs 500 Series SDK to version 6.85.2 or later to remediate this vulnerability. Prior to deployment, test the update in a controlled environment to ensure compatibility with specific device implementations.

Recommended fix Moderate confidence

Silicon Labs 500 Series SDK v6.85.2

  1. Identify the current Silicon Labs 500 Series SDK version in use on affected Z-Wave devices
  2. Obtain the fixed SDK version v6.85.2 from the official Silicon Labs support portal or developer website
  3. Review the v6.85.2 release notes for any specific upgrade instructions or required configuration changes
  4. Update the SDK in your development environment and rebuild the firmware for 500 Series Z-Wave devices
  5. Test the updated firmware in a staging environment to verify the vulnerability is remediated
  6. Deploy the updated firmware to production 500 Series Z-Wave devices

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

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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