CVE-2016-9122

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.

Category

7.5
CVSS
Severity: High
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.18%
Third-Party Advisory openwall.com Third-Party Advisory github.com
Affected: n/a Go JOSE All versions before 1.0.4
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2016-9122?
CVE-2016-9122 has been scored as a high severity vulnerability.
How to fix CVE-2016-9122?
To fix CVE-2016-9122, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2016-9122 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2016-9122 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2016-9122?
CVE-2016-9122 affects n/a Go JOSE All versions before 1.0.4.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.