LiveActive security incident?Get immediate response
CVE Record

CVE-2017-8932: A bug in the standard library ScalarMult implementation of curve P-256 for amd64 architectures in Go before...

A bug in the standard library ScalarMult implementation of curve P-256 for amd64 architectures in Go before 1.7.6 and 1.8.x before 1.8.2 causes incorrect results to be generated for specific input points. An adaptive attack can be mounted to progressively extract the scalar input to ScalarMult by submitting crafted points and observing failures to the derive correct output. This leads to a full key recovery attack against static ECDH, as used in popular JWT libraries.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2017-8932 is a Go cryptography bug on amd64 systems. Certain crafted P-256 inputs could make key agreement calculations fail in ways that reveal a static private key over repeated interactions. Business risk is highest for services built with affected Go versions that use static ECDH, including JWT-related implementations described by the CVE. Exposure is limited to amd64 Go software built with affected Go releases and code paths using P-256 ScalarMult with attacker-controlled points. Static ECDH use materially increases risk. The bundle does not identify affected products beyond Go and downstream vendor packages. Prioritize systems where cryptographic keys are long-lived and externally reachable. The fix path is straightforward, but missed rebuilt binaries can preserve the vulnerable implementation even after a toolchain upgrade. Mitigation focus: Upgrade affected Go toolchains to 1.7.6, 1.8.2, or later.; Rebuild and redeploy binaries compiled with vulnerable Go versions.; Apply relevant Red Hat, Fedora, or openSUSE package updates where applicable..

Prepared

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-8932 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
8Source 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.