|Description||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.|
|Source||CVE (at NVD; CERT, LWN, oss-sec, fulldisc, bugtraq, EDB, Metasploit, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, Mageia, GitHub code/issues, web search, more)|
|NVD severity||medium (attack range: remote)|
|Debian Bugs||863307, 863308|
Vulnerable and fixed packages
The table below lists information on source packages.
The information below is based on the following data on fixed versions.
[stretch] - golang-1.8 <ignored> (Minor issue, would require builds of all go packages in stable)
[stretch] - golang-1.7 <ignored> (Minor issue, would require builds of all go packages in stable)
[wheezy] - golang <not-affected> (Vulnerable code not present, no ASM implementation of the p256 elliptic curve)
[jessie] - golang <not-affected> (Vulnerable code not present, no ASM implementation of the p256 elliptic curve)
Upstream issue: https://github.com/golang/go/issues/20040
Upstream patch: https://golang.org/cl/41070
Fix for 1.7: https://go-review.googlesource.com/c/43773
Fix for 1.8: https://go-review.googlesource.com/c/43770