How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is high, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality low, integrity none, availability none.
CVSS metrics in full
The score comes from this vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
- Attack vector: Network — reachable from anywhere that can route to the service.
- Attack complexity: High — the attacker first has to win a race, learn a secret or otherwise prepare the target.
- Privileges required: Low — an ordinary user account is enough.
- User interaction: None — nobody has to be tricked into anything.
- Scope: Unchanged — the damage stays inside the vulnerable component.
- Confidentiality impact: Low — limited, and the attacker does not choose what is affected.
- Integrity impact: None.
- Availability impact: None.
Weakness class
CVE-2023-32096 is classified as CWE-14: Compiler Removal of Code to Clear Buffers. Sensitive memory is cleared according to the source code, but compiler optimizations leave the memory untouched when it is not read from again, aka "dead store removal."
Affected software
CVE-2023-32096 is recorded against 1 package.
- gecko-software-development-kit (fixed in 4.2.1)
Timeline and source
Published on 18 May 2023 and last revised on 17 June 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.
References
community.silabs.com
github.com
community.silabs.com
github.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-14: Compiler Removal of Code to Clear Buffers) in other software:
