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.
Metrics
Affected Vendors & Products
Advisories
| Source | ID | Title |
|---|---|---|
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 |
GHSA-77gc-fj98-665h | Go JOSE Signature Validation Bypass |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
No history.
Status: PUBLISHED
Assigner: hackerone
Published:
Updated: 2024-08-06T02:42:10.637Z
Reserved: 2016-10-31T00:00:00
Link: CVE-2016-9122
No data.
Status : Deferred
Published: 2017-03-28T02:59:00.260
Modified: 2025-04-20T01:37:25.860
Link: CVE-2016-9122
No data.
OpenCVE Enrichment
No data.
EUVD
Github GHSA