# CVE-2024-2502: Failure to update the tamper reset cause register when a tamper event occurs

> Attackers can bypass tamper detection mechanisms on specific Silicon Labs devices by exploiting a failure to update the tamper reset cause register.

- **Severity:** Low 2.0 (`CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Aug 2024
- **Updated:** 30 Aug 2024
- **Also known as:** GHSA-wcgc-xf7f-fwm5

## What is CVE-2024-2502?

CVE-2024-2502 is a low-severity vulnerability in silabs.com SE Firmware, published on 29 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An application can be configured to block boot attempts after consecutive tamper resets are detected, which may not occur as expected.

This is possible because the TAMPERRSTCAUSE register may not be properly updated when a level 4 tamper event (a tamper reset) occurs. This impacts Series 2 HSE-SVH devices, including xG23B, xG24B, xG25B, and xG28B, but does not impact xG21B. To mitigate this issue, upgrade to SE Firmware version 2.2.6 or later.

Weakness: CWE-754 (Improper Check for Unusual or Exceptional Conditions)

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


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

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

## Is CVE-2024-2502 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-2502 is a low-severity vulnerability in silabs.com SE Firmware, published on 29 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-2502 in the wild and no public exploit code.

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

## Sources

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

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