CVE-2016-9122: High severity namshi/jose vulnerability
Go JOSE before 1.1.0 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
Other sources
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 Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2016-9122?
The severity of CVE-2016-9122 is classified as moderate due to its potential to cause confusion in signature validation.
How do I fix CVE-2016-9122?
To fix CVE-2016-9122, upgrade the go-jose library to version 1.1.0 or higher.
What software is affected by CVE-2016-9122?
CVE-2016-9122 affects versions of the go-jose library prior to 1.1.0.
What is the main issue with CVE-2016-9122?
The main issue with CVE-2016-9122 is that the API does not properly indicate which of the multiple signatures in a signed message is valid.
Is there a known workaround for CVE-2016-9122?
There is no known workaround for CVE-2016-9122; upgrading to the fixed version is the recommended action.