Elliptic Curve Key Disclosure in go-jose
Go JOSE All versions before 1.0.4
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| gopkg.in/square/go-jose.v1 Go |
|
|
| github.com/square/go-jose Go |
|
|
Go JOSE All versions before 1.0.4
| Product | Affected | Fixed in |
|---|---|---|
| gopkg.in/square/go-jose.v1 Go |
|
|
| github.com/square/go-jose Go |
|
|
go-jose before 1.0.4 suffers from an invalid curve attack for the ECDH-ES algorithm. When deriving a shared key using ECDH-ES for an encrypted message, go-jose neglected to check that the received public key on a message is on the same curve as the static private key of the receiver, thus making it vulnerable to an invalid curve attack.
From the CVE record · hackerone
Go JOSE before 1.0.4 does not verify that a public key received in an encrypted message is on the same curve as the receiver’s static private key. An attacker who supplies such a message can trigger an invalid-curve attack during ECDH-ES key derivation. The input does not specify authentication or user-interaction requirements.
Engineers running Go JOSE through gopkg.in/square/go-jose.v1 or github.com/square/go-jose should check versions before 1.0.4.