# CVE-2024-4013: Failure to update BT Mesh Replay Protection List

> Attackers can replay unsaved Bluetooth Mesh messages due to a failure to persist the Replay Protection List during power-off in the Silicon Labs SDK.

- **Severity:** Medium 5.6 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jun 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-hgf8-38x3-cp23

## What is CVE-2024-4013?

CVE-2024-4013 is a medium-severity vulnerability in silabs.com Gecko SDK, published on 6 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A bug exists in the API, mesh_node_power_off(), which fails to copy the contents of the Replay Protection 
List (RPL) from RAM to NVM before powering down, resulting in the ability to replay unsaved messages. Note that as of June 2024, the Gecko SDK was renamed to the Simplicity SDK, and the versioning scheme 
was changed from Gecko SDK vX.Y.Z to Simplicity SDK YYYY.MM.Patch#.

Weakness: CWE-404 (Improper Resource Shutdown or Release)

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


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

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

## Is CVE-2024-4013 being exploited?

There is no known exploitation of CVE-2024-4013 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-4013 is a medium-severity vulnerability in silabs.com Gecko SDK, published on 6 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-4013 in the wild and no public exploit code.

Affected product: silabs.com Gecko SDK. 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-4013/ (Markdown: https://insights.sbomify.com/CVE-2024-4013/index.md)
```

## Sources

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

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