{"answers":{"affected":"2 open source packages ship an affected version, including simplito/elliptic-php. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-10764 in the wild and no public exploit code.","fix":"Upgrade simplito/elliptic-php to 1.0.6 or later.","what":"CVE-2019-10764 is a high-severity vulnerability in simplito/elliptic-php, published on 18 Nov 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-10764 and fix it if it is affected.\n\nWhat it is: CVE-2019-10764 is a high-severity vulnerability in simplito/elliptic-php, published on 18 Nov 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-10764 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- simplito/elliptic-php (Packagist): affected all versions; fixed in 1.0.6\n- simplito/elliptic-php (Packagist): affected all versions; fixed in 1.0.6\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-10764/ (Markdown: https://insights.sbomify.com/CVE-2019-10764/index.md)","id":"CVE-2019-10764","markdown":"https://insights.sbomify.com/CVE-2019-10764/index.md","name":"CVE-2019-10764","record":{"aliases":["GHSA-mr6r-82x4-f4jj","SNYK-PHP-SIMPLITOELLIPTICPHP-534576"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"PHP elliptic curve library","requires_auth":"none","summary":"Timing attacks in elliptic-php may leak scalar bit-length, enabling practical recovery of long-term private keys.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[{"product":"elliptic-php","vendor":"simplito"}],"cvss":{"score":7.4,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-203","name":"Observable Discrepancy"}],"description":"In elliptic-php versions priot to 1.0.6, Timing attacks might be possible which can result in practical recovery of the long-term private key generated by the library under certain conditions. Leakage of a bit-length of the scalar during scalar multiplication is possible on an elliptic curve which might allow practical recovery of the long-term private key.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Timing attacks might allow practical recovery of the long-term private key","id":"CVE-2019-10764","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":2,"n_references":2,"next":{"headline":"Arbitrary File Write in iobroker.admin","id":"CVE-2019-10765"},"packages":[{"ecosystem":"Packagist","fixed":["1.0.6"],"introduced":["0"],"last_affected":[],"package":"simplito/elliptic-php","purl":null,"source":"GHSA-mr6r-82x4-f4jj"},{"ecosystem":"Packagist","fixed":["1.0.6"],"introduced":["0"],"last_affected":[],"package":"simplito/elliptic-php","purl":"pkg:composer/simplito/elliptic-php","source":"GHSA-mr6r-82x4-f4jj"}],"prev":{"headline":"Data leakage via SQL Injection in Pimcore","id":"CVE-2019-10763"},"products":["simplito/elliptic-php"],"published":"2019-11-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":"Timing attacks in elliptic-php may leak scalar bit-length, enabling practical recovery of long-term private keys.","url":"https://insights.sbomify.com/CVE-2019-10764/"}