{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2021-43392 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-43392 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-43392 is a medium-severity vulnerability in n/a, published on 4 Mar 2022. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-43392 and fix it if it is affected.\n\nWhat it is: CVE-2021-43392 is a medium-severity vulnerability in n/a, published on 4 Mar 2022. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-43392 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2021-43392/ (Markdown: https://insights.sbomify.com/CVE-2021-43392/index.md)","id":"CVE-2021-43392","markdown":"https://insights.sbomify.com/CVE-2021-43392/index.md","name":"CVE-2021-43392","record":{"aliases":["GHSA-vjrp-j935-mwh9"],"analysis":{"component_type":"hardware_firmware","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Java Card Secure Element","requires_auth":"none","summary":"Attackers can obtain cryptographic secrets from STMicroelectronics Java Card secure elements via ECDSA side-channel leaks in specific configurations.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"j-safe3_firmware","vendor":"st"},{"product":"stsafe-j_firmware","vendor":"st"}],"cvss":{"score":6.2,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2021-43392","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2021-43393"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2021-43391"},"products":["n/a"],"published":"2022-03-04","related":[{"cvss_score":6.2,"headline":"Security feature bypass in n/a","id":"CVE-2021-43393","kev_date_added":null,"published":"2022-03-04"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can obtain cryptographic secrets from STMicroelectronics Java Card secure elements via ECDSA side-channel leaks in specific configurations.","url":"https://insights.sbomify.com/CVE-2021-43392/"}