CVE-2017-1000168
mediumpriority · track · 26EPSS 0.013 · 69 %ileEUUSEPSS · scored 2026-10-26
sodiumoxide 0.0.13 and older scalarmult() vulnerable to degenerate public keys
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (4)
Products and version ranges known to be affected.
- sodiumoxide project sodiumoxide≤ 0.0.13nvdUScpe:2.3:a:sodiumoxide_project:sodiumoxide:*:*:*:*:*:*:*:*
advisories (2)
Vendor and ecosystem advisories describing this.
- GHSA-2wc6-2rcj-8v76scalarmult() vulnerable to degenerate public keys2021-08-25ghsa · osvUS
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.
- RUSTSEC-2017-0001scalarmult() vulnerable to degenerate public keys2017-01-26vendor · osvUS
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.
also known as (5)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (3)
External citations — patches, advisories, analysis.
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan