# CVE-2019-25002: Incorrect Comparison in sodiumoxide

> A logic error in the sodiumoxide Rust crate causes hash comparisons to always return true, bypassing integrity checks.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Dec 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-wrvc-72w7-xpmj, RUSTSEC-2019-0026

## What is CVE-2019-25002?

CVE-2019-25002 is a critical vulnerability in n/a, published on 31 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in the sodiumoxide crate before 0.2.5 for Rust. generichash::Digest::eq compares itself to itself and thus has degenerate security properties.

## Which versions are affected by CVE-2019-25002?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sodiumoxide` | crates.io | From 0.0.0-0 | 0.2.5 |
| `sodiumoxide` | crates.io | From 0.2.0 | 0.2.5 |
| `sodiumoxide` | crates.io | From 0.2.0 | 0.2.5 |

Products: Sodiumoxide Project Sodiumoxide.

## How do I fix CVE-2019-25002?

Upgrade sodiumoxide to 0.2.5 or later.

## Is CVE-2019-25002 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-1000168](https://insights.sbomify.com/CVE-2017-1000168/): scalarmult() vulnerable to degenerate public keys (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25002 and fix it if it is affected.

What it is: CVE-2019-25002 is a critical vulnerability in n/a, published on 31 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-25002 in the wild and no public exploit code.

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

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-2019-25002/ (Markdown: https://insights.sbomify.com/CVE-2019-25002/index.md)
```

## Sources

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

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