First published: Fri Mar 04 2022(Updated: )
STMicroelectronics STSAFE-J 1.1.4, J-SAFE3 1.2.5, and J-SIGN sometimes allow attackers to abuse signature verification. This is associated with the ECDSA signature algorithm on the Java Card J-SAFE3 and STSAFE-J platforms exposing a 3.0.4 Java Card API. It is exploitable for STSAFE-J in closed configuration and J-SIGN (when signature verification is activated) but not for J-SAFE3 EPASS BAC and EAC products. It might also impact other products based on the J-SAFE-3 Java Card platform.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
St Stsafe-j Firmware | =1.1.4 | |
St Stsafe-j | ||
St J-safe3 Firmware | =1.2.5 | |
St J-safe3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID is CVE-2021-43393.
STMicroelectronics STSAFE-J 1.1.4 and J-SAFE3 1.2.5 are affected by this vulnerability.
The severity of CVE-2021-43393 is medium with a severity value of 6.2.
Attackers can abuse signature verification through the ECDSA signature algorithm on the Java Card J-SAFE3 and STSAFE-J platforms exposing a 3.0.4 Java Card API.
Yes, you can find more information about this vulnerability at the following references: [1](https://community.st.com/s/toparticles) and [2](https://www.cert.ssi.gouv.fr/avis/CERTFR-2022-AVI-169/).