Technical impact
Deleting a Matter Credential Issuer in the Nordic Semiconductor nRF Door Lock and Access Control Add‑on mistakenly passes a 1‑based index to ClearValidityIterations(), which expects a 0‑based index. The intended issuer’s ValidityIteration state is left intact while the adjacent, still‑provisioned issuer’s state is cleared, resetting that issuer’s rollback protection. An attacker who can delete a credential issuer—likely through an authorized control interface—can then use an older but correctly signed Access Document from the cleared issuer to gain physical access to the locked device. The vulnerability is an example of an integer conversion boundary error (CWE‑193) that leads to loss of integrity protection for access control. The likely attack vector is an entity with legitimate access to the device’s credential management functions, such as a maintenance engineer or a compromised local controller. Based on the description, no exploit code is publicly available, but the flaw can be triggered by a simple delete operation. The reported CVSS score of 7 indicates a medium‑to‑high severity. EPSS is not available, and the vulnerability is not listed in the CISA KEV catalog, suggesting that no widespread exploitation has been observed yet. However, because the flaw directly undermines physical access safeguards, the risk remains significant for deployments relying on the affected door‑lock firmware.
Affected Systems
Nordic Semiconductor ASA nRF Door Lock and Access Control Add‑on, versions v1.0.0 through v1.1.1 with CONFIG_DOOR_LOCK_STEP_UP_PHASE enabled, are affected by this flaw.
Risk and Exploitability
The flaw’s CVSS score of 7 reflects a serious impact if exploited. Since EPSS data is absent and KEV has not filed the issue, there is no evidence of active exploitation, but the absence of mitigation only increases the potential for a local attacker to gain physical control. The vulnerability requires deletion of a credential issuer, so an attacker would need at least local device access or compromised control credentials. Given these prerequisites, the likelihood of exploitation is moderate, but the potential consequences—unauthorized physical access—are high.