CVE-2025-56364
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 · uneditedA use of uninitialized value vulnerability exists in the Matter SDK (connectedhomeip) before 1.4.0, where the `GetDestinationGroupId().Value()` method is called without first checking whether a value exists. This leads to a crash when an InvokeCommand is sent without initializing the destination group ID. The issue affects all versions before commit 0360cc3 (Dec 5, 2024) and leads to denial of service through SIGABRT. It is fixed by adding a .HasValue() check before access.
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 confidenceA use of uninitialized value vulnerability exists in the Matter SDK (connectedhomeip) before 1.4.0 where the GetDestinationGroupId().Value() method is called without first checking whether a value exists via HasValue(). This leads to a crash (SIGABRT) when an InvokeCommand is sent without initializing the destination group ID, resulting in denial of service.
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< 1.4.0.0CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Matter SDK version in useSearch for the Matter SDK (connectedhomeip) library in your project dependencies, build artifacts, or installed packages. Check the version number against the 1.4.0.0 threshold (versions below 1.4.0.0 are affected).Affected if Matter SDK version is below 1.4.0.0 (such as 1.3.x, 1.2.x, etc.)
-
Locate GetDestinationGroupId usage in source codeSearch your codebase for calls to GetDestinationGroupId() method. Review the InvokeCommand code paths that handle group-based messaging to see if HasValue() is checked before calling Value().Affected if Code calls GetDestinationGroupId().Value() without first calling HasValue() to verify a value exists
-
Check InvokeCommand implementation for group messagingIf you have custom InvokeCommand implementations or use Matter's group command functionality, examine whether destination group ID is properly initialized before being passed to InvokeCommand requests.Affected if InvokeCommand is used for group messaging without proper destination group ID initialization
You are affected if your environment uses Matter SDK (connectedhomeip) version below 1.4.0.0 and your code or a third-party component calls GetDestinationGroupId().Value() without first verifying a value exists via HasValue().
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.4.0.0
Upgrade to Matter SDK version 1.4.0 or later, or apply the fix by adding .HasValue() checks before calling .Value() on GetDestinationGroupId().
Matter SDK 1.4.0.0
- Upgrade the Matter SDK (connectedhomeip) to version 1.4.0.0 or later to include the .HasValue() check fix
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-56364 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-56364 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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