LiveActive security incident?Get immediate response
CVE Record

CVE-2017-1000168: sodiumoxide 0.0.13 and older scalarmult() vulnerable to degenerate public keys

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

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This CVE concerns sodiumoxide 0.0.13 and older, where the scalarmult() cryptographic operation is described as vulnerable to degenerate public keys. In business terms, systems relying on that library for key agreement may have cryptographic trust assumptions weakened. The public record provided does not include severity, CVSS, CWE, exploit evidence, or a named fix.

Executive priority

Prioritize this for systems using older sodiumoxide in authentication, encryption, session setup, or peer-to-peer trust flows. Urgency is unclear because public severity and exploit evidence are missing, but cryptographic dependency issues can undermine high-value security controls.

Technical view

The CVE description states that sodiumoxide 0.0.13 and older have scalarmult() exposure involving degenerate public keys. The record provides no CVSS vector, CWE mapping, CPEs, or detailed affected-product metadata. Analysis should focus on direct or transitive sodiumoxide use and whether scalarmult() processes externally supplied public keys.

Likely exposure

Exposure is likely limited to applications using sodiumoxide 0.0.13 or older, especially code paths calling scalarmult() with public keys received from peers, clients, or stored untrusted data. The source bundle does not prove exposure for later versions or other products.

Exploitation context

The source bundle does not show active exploitation, and the CVE is not marked as KEV. It also does not provide exploit details. Treat this as a cryptographic correctness risk requiring dependency and usage review, not as a confirmed internet-wide exploitation event.

Researcher notes

Evidence is sparse: the bundle provides only the core description and one GitHub issue reference. Do not assume affected CPEs, exploitability, or fixed versions without upstream confirmation. The main research task is dependency confirmation plus data-flow analysis around scalarmult() inputs.

Mitigation direction

  • Inventory direct and transitive sodiumoxide dependencies and flag versions 0.0.13 or older.
  • Check the upstream issue and CVE record for vendor-confirmed fix or upgrade guidance.
  • Prioritize replacement or upgrade where scalarmult() handles untrusted peer-supplied public keys.
  • Add application-level rejection or validation for invalid peer keys if vendor guidance supports it.
  • Document any temporary compensating controls and their review date.

Validation and detection

  • Review Cargo manifests and lockfiles for sodiumoxide version 0.0.13 or older.
  • Search code for scalarmult() usage and map all input sources.
  • Confirm whether public keys can be supplied by remote users, peers, or stored untrusted records.
  • Check upstream issue 154 and CVE metadata for clarified remediation status.
  • Add regression tests that ensure invalid public-key inputs are safely handled.
Prepared
Confidence
medium
Sources
3

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CVE-2017-1000168 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.