dbcve.org
MatterApplication · Csa Iot

CVE-2024-3297

MEDIUM · 6.5 CVSS v3.1 Published 2024-07-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/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
An issue in the Certificate Authenticated Session Establishment (CASE) protocol for establishing secure sessions between two devices, as implemented in the Matter protocol versions before Matter 1.1 allows an attacker to replay manipulated CASE Sigma1 messages to make the device unresponsive until the device is power-cycled.

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

This is a replay attack vulnerability in the Matter protocol's Certificate Authenticated Session Establishment (CASE) protocol. An attacker can capture and replay manipulated CASE Sigma1 messages to cause affected devices to become unresponsive, requiring a manual power cycle to recover. The vulnerability affects Matter protocol implementations prior to version 1.1.

MitigationUpgrade all Matter devices to version 1.1 or later which contains the fix. For devices that cannot be updated, consider network segmentation and strict access controls to reduce exposure to replay attacks on the local network.

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
MatterApplication
Affected:all versions

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

CVSS:3.1/AV:A/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Matter protocol usage
    Inventory all IoT devices, gateways, or software in the environment that implement the Matter smart home protocol. Check device documentation, firmware manifests, or network traffic for Matter protocol indicators.
    Affected if Any Matter-enabled devices or software are found in the environment
  2. Determine Matter implementation version
    Locate the Matter protocol library or firmware version on each identified device or software component. Consult the vendor documentation, device firmware information, or software bill of materials (SBOM) for the exact version number.
    Affected if The Matter implementation version is earlier than 1.1
  3. Verify CASE protocol is active
    Check whether Certificate Authenticated Session Establishment (CASE) is enabled in the Matter implementation settings or configuration. CASE is used for authenticated commissioning between devices with device attestation certificates.
    Affected if CASE protocol is enabled and used for device commissioning
  4. Check for Csa Iot Matter component
    If the environment uses Csa Iot Matter libraries or devices, identify the specific version of this component by examining the software dependencies, firmware metadata, or vendor product information.
    Affected if Csa Iot Matter is present in any version

The environment is affected if Matter protocol devices or software with CASE session establishment are deployed and the Matter implementation version is earlier than 1.1.

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 all Matter devices to version 1.1 or later which contains the fix. For devices that cannot be updated, consider network segmentation and strict access controls to reduce exposure to replay attacks on the local network.

Recommended fix Moderate confidence

Matter 1.1 or later

  1. Upgrade the Matter protocol implementation to version 1.1 or later to remediate the vulnerability
  2. Verify the upgrade does not break existing device certifications or interoperability
  3. Test the updated implementation to confirm the device remains responsive after receiving replayed CASE Sigma1 messages
  4. Ensure all devices in the Matter network are updated to prevent exploitation of older devices
Caveat Review Matter 1.1 release notes for any protocol behavior changes that may affect existing device integrations

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

Fix this in Matter 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-3297 — 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-3297 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