# CVE-2017-1000168: scalarmult() vulnerable to degenerate public keys

> The sodiumoxide library's scalarmult function is vulnerable to degenerate public keys, potentially compromising cryptographic operations.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 17 Nov 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-2wc6-2rcj-8v76, RUSTSEC-2017-0001

## What is CVE-2017-1000168?

CVE-2017-1000168 is a medium-severity vulnerability in n/a, published on 17 Nov 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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

## Which versions are affected by CVE-2017-1000168?

3 open source packages ship an affected version, including sodiumoxide. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sodiumoxide` | crates.io | All versions | 0.0.14 |
| `sodiumoxide` | crates.io | All versions | 0.0.14 |
| `sodiumoxide` | crates.io | From 0.0.0-0 | 0.0.14 |

Products: Sodiumoxide Project Sodiumoxide.

## How do I fix CVE-2017-1000168?

Upgrade sodiumoxide to 0.0.14 or later.

## Is CVE-2017-1000168 being exploited?

There is no known exploitation of CVE-2017-1000168 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2019-25002](https://insights.sbomify.com/CVE-2019-25002/): Incorrect Comparison in sodiumoxide (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-1000168 and fix it if it is affected.

What it is: CVE-2017-1000168 is a medium-severity vulnerability in n/a, published on 17 Nov 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-1000168 in the wild and no public exploit code.

Affected packages and fixed versions:
- sodiumoxide (crates.io): affected all versions; fixed in 0.0.14
- sodiumoxide (crates.io): affected all versions; fixed in 0.0.14
- sodiumoxide (crates.io): affected from 0.0.0-0; fixed in 0.0.14

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-1000168/ (Markdown: https://insights.sbomify.com/CVE-2017-1000168/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-1000168
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-1000168
- OSV: https://osv.dev/vulnerability/CVE-2017-1000168

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-1000168/
Summaries are generated and may contain mistakes; the official description above is the record.