CVE-2019-10764 json
Timing attacks might allow practical recovery of the long-term private key
published 2019-11-18 6 y ago modified 2026-07-08 4 mo ago also GHSA-mr6r-82x4-f4jj , EUVD-2019-0757
- cvss
- 7.4
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 65%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- packagist simplito/elliptic-php 1.0.6
- simplito elliptic-php 1.0.6
Exploit prediction
1.09% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- minerva.crocs.fi.muni.cz https://minerva.crocs.fi.muni.cz/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
| NVD | 2.0 | 5.8 | AV:N/AC:M/Au:N/C:P/I:P/A:N |
| GitHub | 3.1 | 7.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | simplito/elliptic-php | <1.0.6 |
1.0.6 |
Affected products
- n/a simplito/elliptic-php
Classification
- Weakness
-
- CWE-203 Observable Discrepancy
References
-
github.com
/simplito/elliptic-php/commit/15652609aa55968d56685c2a9120535ccdc00fd9
web
-
minerva.crocs.fi.muni.cz
/
exploit, third-party-advisory
-
snyk.io
/vuln/SNYK-PHP-SIMPLITOELLIPTICPHP-534576
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-10764
advisory
-
minerva.crocs.fi.muni.cz
web
Sources
- CVE List CVE-2019-10764
- GitHub Advisory GHSA-mr6r-82x4-f4jj
- NVD CVE-2019-10764
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.