{"answers":{"affected":"It affects 5 products.","exploited":"There is no known exploitation of CVE-2019-15809 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-15809 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-15809 is a medium-severity vulnerability in n/a, published on 3 Oct 2019. 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-2019-15809 and fix it if it is affected.\n\nWhat it is: CVE-2019-15809 is a medium-severity vulnerability in n/a, published on 3 Oct 2019. 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-2019-15809 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-2019-15809/ (Markdown: https://insights.sbomify.com/CVE-2019-15809/index.md)","id":"CVE-2019-15809","markdown":"https://insights.sbomify.com/CVE-2019-15809/index.md","name":"CVE-2019-15809","record":{"aliases":["GHSA-c76g-76cj-g742"],"analysis":{"component_type":"hardware_firmware","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Smart card firmware","requires_auth":"low_privilege","summary":"A timing side-channel in ECDSA signature generation allows local attackers to recover private keys from affected smart cards.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"idprotect","vendor":"athena-scs"},{"product":"s\\/a_idflex_v","vendor":"cryptsoft"},{"product":"atmel_toolbox","vendor":"microchip"},{"product":"armored_card","vendor":"tecsec"},{"product":"etoken_4300","vendor":"thalesgroup"}],"cvss":{"score":4.7,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-203","name":"Observable Discrepancy"}],"description":"Smart cards from the Athena SCS manufacturer, based on the Atmel Toolbox 00.03.11.05 and the AT90SC chip, contain a timing side channel in ECDSA signature generation. This allows a local attacker, able to measure the duration of hundreds to thousands of signing operations, to compute the private key used. The issue occurs because the Atmel Toolbox 00.03.11.05 contains two versions of ECDSA signature functions, described as fast and secure, but the affected cards chose to use the fast version, which leaks the bit length of the random nonce via timing. This affects Athena IDProtect 010b.0352.0005, Athena IDProtect 010e.1245.0002, Athena IDProtect 0106.0130.0401, Athena IDProtect 010e.1245.0002, Valid S/A IDflex V 010b.0352.0005, SafeNet eToken 4300 010e.1245.0002, TecSec Armored Card 010e.0264.0001, and TecSec Armored Card 108.0264.0001.","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-2019-15809","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":6,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-15810"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2019-15807"},"products":["n/a"],"published":"2019-10-03","related":[],"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-05","vendors":["n/a"]},"summary":"A timing side-channel in ECDSA signature generation allows local attackers to recover private keys from affected smart cards.","url":"https://insights.sbomify.com/CVE-2019-15809/"}