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.
Advisories
Source ID Title
EUVD EUVD EUVD-2021-0989 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.
Github GHSA Github GHSA GHSA-77gc-fj98-665h Go JOSE Signature Validation Bypass
Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

No history.

cve-icon MITRE

Status: PUBLISHED

Assigner: hackerone

Published:

Updated: 2024-08-06T02:42:10.637Z

Reserved: 2016-10-31T00:00:00

Link: CVE-2016-9122

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Deferred

Published: 2017-03-28T02:59:00.260

Modified: 2025-04-20T01:37:25.860

Link: CVE-2016-9122

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.