CVE-2016-9122
go-jose before 1.0.4 suffers from multiple signatures exploitation.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (1.97%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
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.
- CVSS 3.0
- 7.5 HIGHCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
- EPSS
- 1.97% probability · 79th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-284
- Affected
- go-jose project/go-jose
- Source
- support@hackerone.com
References
- http://www.openwall.com/lists/oss-security/2016/11/03/1Mailing List, Patch, Third Party Advisory
- https://github.com/square/go-jose/commit/2c5656adca9909843c4ff50acf1d2cf8f32da7e6Issue Tracking, Patch, Third Party Advisory
- https://hackerone.com/reports/169629Permissions Required
- http://www.openwall.com/lists/oss-security/2016/11/03/1Mailing List, Patch, Third Party Advisory
- https://github.com/square/go-jose/commit/2c5656adca9909843c4ff50acf1d2cf8f32da7e6Issue Tracking, Patch, Third Party Advisory
- https://hackerone.com/reports/169629Permissions Required
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.