scalarmult() vulnerable to degenerate public keys

published 2017-01-26 9y ago modified 2026-06-17 4mo ago also GHSA-2wc6-2rcj-8v76 , RUSTSEC-2017-0001 , EUVD-2021-1520

cvss: 6.5; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.3%; EPSS 1.3% chance of exploitation in 30 days, percentile 69%
public exploits: 0; none known

sodiumoxide 0.0.13 and older scalarmult() vulnerable to degenerate public keys

Patch / fix

fixed in 1 links 1

crates.io sodiumoxide 0.0.14

github.com/sodiumoxide/sodiumoxide@24c7a55 commit

Is CVE-2017-1000168 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.25% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.0	6.5	CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
NVD	2.0	4.3	AV:N/AC:M/Au:N/C:P/I:N/A:N
GitHub	3.0	6.5	CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
OSV	3.0	6.5	CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Affected packages

ecosystem	package	affected	fixed in
crates.io	sodiumoxide	<0.0.14 >=0.0.0-0, <0.0.14	0.0.14

Classification

Weakness

CWE-1240 Use of a Cryptographic Primitive with a Risky Implementation

References

github.com /sodiumoxide/sodiumoxide/commit/24c7a5550807ac8a09648b5878f19d14c3a69135
web
github.com /dnaq/sodiumoxide/issues/154
web, issue-tracking, third-party-advisory, report
nvd.nist.gov /vuln/detail/CVE-2017-1000168
advisory
github.com /sodiumoxide/sodiumoxide
package
rustsec.org /advisories/RUSTSEC-2017-0001.html
web, advisory
crates.io /crates/sodiumoxide
package

Sources

Fencer Intel 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.