CVE-2016-9122

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.
References
Configurations

Configuration 1 (hide)

cpe:2.3:a:go-jose_project:go-jose:*:*:*:*:*:*:*:*

History

21 Nov 2024, 03:00

Type Values Removed Values Added
References () http://www.openwall.com/lists/oss-security/2016/11/03/1 - Mailing List, Patch, Third Party Advisory () http://www.openwall.com/lists/oss-security/2016/11/03/1 - Mailing List, Patch, Third Party Advisory
References () https://github.com/square/go-jose/commit/2c5656adca9909843c4ff50acf1d2cf8f32da7e6 - Issue Tracking, Patch, Third Party Advisory () https://github.com/square/go-jose/commit/2c5656adca9909843c4ff50acf1d2cf8f32da7e6 - Issue Tracking, Patch, Third Party Advisory
References () https://hackerone.com/reports/169629 - Permissions Required () https://hackerone.com/reports/169629 - Permissions Required

Information

Published : 2017-03-28 02:59

Updated : 2024-11-21 03:00


NVD link : CVE-2016-9122

Mitre link : CVE-2016-9122

CVE.ORG link : CVE-2016-9122


JSON object : View

Products Affected

go-jose_project

  • go-jose
CWE
CWE-284

Improper Access Control