How severe is CVE-2017-1000168?

CVE-2017-1000168 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2017-1000168?

CVE-2017-1000168 affects the following packages: sodiumoxide (crates.io). Ecosystems affected: crates.io.

How do I fix CVE-2017-1000168?

Update sodiumoxide to 0.0.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-1000168 is resolved across your whole dependency graph.

How do I detect CVE-2017-1000168 in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sodiumoxide, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2017-1000168 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2017-1000168 actively exploited in the wild?

No public exploit code has been indexed for CVE-2017-1000168 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2017-1000168?

CVE-2017-1000168 has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 69th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2017-1000168 published, and has it been updated?

CVE-2017-1000168 was published on August 25, 2021 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀

🦀 crates.io

Not in CISA KEV

MEDIUM severity

CVE-2017-1000168 — sodiumoxide

MEDIUMFix: sodiumoxide/sodiumoxide@24c7a55

CVE-2017-1000168 is a medium-severity (CVSS 6.5) vulnerability in sodiumoxide. A fix is available for sodiumoxide — see the affected versions and patch details below.

scalarmult() vulnerable to degenerate public keys

Also known asRUSTSEC-2017-0001

Published

Aug 25, 2021

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs69th percentile — riskier than 69% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2017-1000168 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 384,534 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

🦀sodiumoxide

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

This issue was fixed by checking for this class of keys and rejecting them if they are used.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`sodiumoxide`	all versions	0.0.14`cargo update -p sodiumoxide --precise 0.0.14`

Affected Products

1 product · 1 configurations

Application

sodiumoxidesodiumoxide_project

≤ 0.0.13

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sodiumoxide, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update sodiumoxide to 0.0.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-1000168 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2017-1000168 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works