# CVE-2024-56318: Null dereference in Matter

> Attackers can cause denial of service in Matter devices by sending TCP packets with zero message size, triggering a null pointer dereference.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Dec 2024
- **Updated:** 2 Jan 2025
- **Also known as:** GHSA-93xr-jvr5-8x88

## What is CVE-2024-56318?

CVE-2024-56318 is a high-severity vulnerability in Matter, published on 18 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In raw\TCP.cpp in Matter (aka connectedhomeip or Project CHIP) through 1.4.0.0 before 27ca6ec, there is a NULL pointer dereference in TCPBase::ProcessSingleMessage via TCP packets with zero messageSize, leading to denial of service.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2024-56318?


## How do I fix CVE-2024-56318?

No fix has been published for CVE-2024-56318 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-56318 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-56318 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-56318 and fix it if it is affected.

What it is: CVE-2024-56318 is a high-severity vulnerability in Matter, published on 18 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-56318 exists.

Affected product: Matter. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-56318/ (Markdown: https://insights.sbomify.com/CVE-2024-56318/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-56318
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-56318
- OSV: https://osv.dev/vulnerability/CVE-2024-56318

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-56318/
Summaries are generated and may contain mistakes; the official description above is the record.