Description
go-jose before 1.0.4 suffers from multiple signatures exploitation. The go-jose library supports messages with multiple signatures. However, when validating a signed message the API did not indicate which signature was valid, which could potentially lead to confusion. For example, users of the library might mistakenly read protected header values from an attached signature that was different from the one originally validated.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| — | Go JOSE All versions before 1.0.4 | Go JOSE All versions before 1.0.4 | — |
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Debian
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian 14 | golang-gopkg-square-go-jose.v1 | 1.0.5-1 | — |
| Debian 13 | golang-gopkg-square-go-jose.v1 | 1.0.5-1 | — |
| Debian 12 | golang-gopkg-square-go-jose.v1 | 1.0.5-1 | — |
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| Go | gopkg.in/square/go-jose.v1 | < 1.1.0 | 1.1.0 | GHSA-77gc-fj98-665h |