A vulnerability was found in sodiumoxide up to 0.0.13 and classified as critical. This issue affects the function scalarmult of the component ScalarMult. The manipulation with an unknown input leads to a key management vulnerability. Using CWE to declare the problem leads to CWE-320. Impacted is confidentiality. The summary by CVE is:

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

The bug was discovered 01/26/2017. The weakness was shared 11/17/2017 (GitHub Repository). The advisory is shared at github.com. The identification of this vulnerability is CVE-2017-1000168 since 11/17/2017. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1600.001 for this issue.

The vulnerability was handled as a non-public zero-day exploit for at least 295 days. During that time the estimated underground price was around $0-$5k.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Productinfo

Name

• sodiumoxide

Version

• 0.0.1
• 0.0.2
• 0.0.3
• 0.0.4
• 0.0.5
• 0.0.6
• 0.0.7
• 0.0.8
• 0.0.9
• 0.0.10
• 0.0.11
• 0.0.12
• 0.0.13

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Discussion