{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-13629 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-13629 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-13629 is a medium-severity vulnerability in n/a, published on 3 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-13629 and fix it if it is affected.\n\nWhat it is: CVE-2019-13629 is a medium-severity vulnerability in n/a, published on 3 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-13629 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-13629/ (Markdown: https://insights.sbomify.com/CVE-2019-13629/index.md)","id":"CVE-2019-13629","markdown":"https://insights.sbomify.com/CVE-2019-13629/index.md","name":"CVE-2019-13629","record":{"aliases":["GHSA-p73v-qh88-fqc2"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"MatrixSSL library","requires_auth":"none","summary":"Attackers can recover private keys by measuring timing variations in ECDSA signature generation within the MatrixSSL library.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"matrixssl","vendor":"matrixssl"}],"cvss":{"score":5.9,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"},{"id":"CWE-203","name":"Observable Discrepancy"}],"description":"MatrixSSL 4.2.1 and earlier contains a timing side channel in ECDSA signature generation. This allows a local or a remote attacker, able to measure the duration of hundreds to thousands of signing operations, to compute the private key used. The issue occurs because crypto/pubkey/ecc_math.c scalar multiplication leaks the bit length of the scalar.","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-13629","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":4,"next":{"headline":"Memory corruption in n/a","id":"CVE-2019-13631"},"packages":[],"prev":{"headline":"wolfCrypt leaks cryptographic information via timing side channel","id":"CVE-2019-13628"},"products":["n/a"],"published":"2019-10-03","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2019-14431","kev_date_added":null,"published":"2019-07-29"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2019-13470","kev_date_added":null,"published":"2019-07-09"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2019-10914","kev_date_added":null,"published":"2019-04-08"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2016-6890","kev_date_added":null,"published":"2017-01-05"},{"cvss_score":8.1,"headline":"Integer overflow in n/a","id":"CVE-2022-43974","kev_date_added":null,"published":"2023-01-09"},{"cvss_score":8.1,"headline":"Memory corruption in MatrixSSL","id":"CVE-2017-2780","kev_date_added":null,"published":"2017-06-22"},{"cvss_score":8.1,"headline":"Memory corruption in MatrixSSL","id":"CVE-2017-2781","kev_date_added":null,"published":"2017-06-22"}],"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 recover private keys by measuring timing variations in ECDSA signature generation within the MatrixSSL library.","url":"https://insights.sbomify.com/CVE-2019-13629/"}