How this vulnerability can be exploited
This issue can be reached with physical access to the device, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity none, availability none.
CVSS metrics in full
The score comes from this vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Attack vector: Physical — the attacker has to touch the device.
- Attack complexity: Low — the attack works reliably, with no preparation.
- Privileges required: None — an unauthenticated stranger can try it.
- User interaction: None — nobody has to be tricked into anything.
- Scope: Unchanged — the damage stays inside the vulnerable component.
- Confidentiality impact: High — total loss, or loss the attacker controls.
- Integrity impact: None.
- Availability impact: None.
Weakness class
CVE-2023-41097 is classified as CWE-208: Observable Timing Discrepancy. Two separate operations in a product require different amounts of time to complete, in a way that is observable to an actor and reveals security-relevant information about the state of the product, such as whether a particular operation was successful or not.
Affected software
CVE-2023-41097 is recorded against 1 package.
- gecko-software-development-kit (fixed in 4.4.0)
Timeline and source
Published on 21 December 2023 and last revised on 17 June 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.
References
github.com
siliconlabs.lightning.force.com
github.com
siliconlabs.lightning.force.com
Other advisories for this package
gecko-software-development-kit has other advisories on record. If you are patching this one, these are worth checking on the same host:
Same weakness in other software
These advisories are the same class of weakness (CWE-208: Observable Timing Discrepancy) in other software:
