Security readout for executives and security teams
Plain-English summary
CVE-2019-25002 affects Rust applications using the sodiumoxide crate before 0.2.5. A digest equality check could behave incorrectly, weakening decisions that rely on matching cryptographic hashes. Business urgency depends on whether the affected API is used for authentication, integrity checks, or trust decisions.
Executive priority
Treat as targeted dependency remediation. Escalate priority for systems where sodiumoxide digest equality protects access, data integrity, or customer-facing trust decisions.
Technical view
In sodiumoxide before 0.2.5, generichash::Digest::eq compares the value to itself, giving degenerate security properties. The sources do not provide CVSS, CWE, exploit code, or confirmed exploitation. Exposure is limited to projects that depend on vulnerable sodiumoxide versions and use this equality behavior in security-sensitive logic.
Likely exposure
Rust services, CLIs, or libraries using sodiumoxide before 0.2.5 may be exposed, especially where generichash::Digest equality controls authentication, integrity validation, or authorization decisions.
Exploitation context
No KEV entry or provided source states active exploitation. Practical risk requires an application path where incorrect digest comparison changes a security outcome.
Researcher notes
The source evidence is narrow: affected crate, version boundary, and flawed equality semantics. No CVSS, CWE, exploit status, or downstream product list is supplied, so asset-level impact must be established from dependency and code usage review.
Mitigation direction
- Upgrade sodiumoxide to version 0.2.5 or later.
- Regenerate lockfiles and rebuild affected Rust artifacts.
- Review security-sensitive uses of generichash::Digest equality.
- Check RustSec and project maintainer guidance for constraints.
- Add regression tests for digest comparison behavior.
Validation and detection
- Inspect Cargo.toml and Cargo.lock for sodiumoxide versions before 0.2.5.
- Identify code paths comparing generichash::Digest values.
- Confirm patched builds resolve sodiumoxide 0.2.5 or later.
- Run unit tests covering accepted and rejected digest comparisons.
- Prioritize review of authentication and integrity-checking flows.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2019-25002 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://rustsec.org/advisories/RUSTSEC-2019-0026.htmlCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.