Elliptic Curve Key Disclosure in go-jose
Published 23 Jun 2021 · Updated 8 Nov 2023
Is your project on an affected gopkg.in/square/go-jose.v1?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- <1.0.4
- Fixed in
- 1.0.4
go get gopkg.in/square/go-jose.v1@v1.0.4- Affected
- <1.0.4
- Fixed in
- 1.0.4
go get github.com/square/go-jose@v1.0.4Details
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.
Is GHSA-86r9-39j9-99wp in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected gopkg.in/square/go-jose.v1, and gives you the command that fixes it.
More advisories for gopkg.in/square/go-jose.v1
- LowCVE-2016-9122Signature validation bypass in gopkg.in/square/go-jose.v1 · 22 Aug 2022
- HighCVE-2016-9122Go JOSE Signature Validation Bypass · 18 May 2021
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.