CVE-2017-1000168
published 2017-11-17CVE-2017-1000168: sodiumoxide 0.0.13 and older scalarmult() vulnerable to degenerate public keys
PriorityP428medium6.5CVSS 3.0
AVNACLPRNUIRSUCHINAN
EPSS
1.25%
65.9th percentile
sodiumoxide 0.0.13 and older scalarmult() vulnerable to degenerate public keys
Affected
3 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| sodiumoxide_project | sodiumoxide | <= 0.0.13 | — |
| sodiumoxide_project | sodiumoxide | >= 0 < 0.0.14 | 0.0.14 |
| sodiumoxide_project | sodiumoxide | >= 0.0.0-0 < 0.0.14 | 0.0.14 |
CVSS provenance
nvdv3.06.5MEDIUMCVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
nvdv2.04.3MEDIUMAV:N/AC:M/Au:N/C:P/I:N/A:N
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
scalarmult() vulnerable to degenerate public keys
osv·2021-08-25
CVE-2017-1000168 [MEDIUM] scalarmult() vulnerable to degenerate public keys
scalarmult() vulnerable to degenerate public keys
The scalarmult() function included in previous versions of this crate accepted all-zero public keys, for which the resulting Diffie-Hellman shared secret will always be zero regardless of the private key used.
This issue was fixed by checking for this class of keys and rejecting them if they are used.
GHSA
scalarmult() vulnerable to degenerate public keys
ghsa·2021-08-25
CVE-2017-1000168 [MEDIUM] CWE-1240 scalarmult() vulnerable to degenerate public keys
scalarmult() vulnerable to degenerate public keys
The scalarmult() function included in previous versions of this crate accepted all-zero public keys, for which the resulting Diffie-Hellman shared secret will always be zero regardless of the private key used.
This issue was fixed by checking for this class of keys and rejecting them if they are used.
OSV
scalarmult() vulnerable to degenerate public keys
osv·2017-01-26
CVE-2017-1000168 scalarmult() vulnerable to degenerate public keys
scalarmult() vulnerable to degenerate public keys
The `scalarmult()` function included in previous versions of this crate
accepted all-zero public keys, for which the resulting Diffie-Hellman shared
secret will always be zero regardless of the private key used.
This issue was fixed by checking for this class of keys and rejecting them
if they are used.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2017-11-17
Published