CVE-2016-9122

high
Published 2017-03-28 ยท Modified 2024-05-20
CVSS v3
7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
CVSS v4 NEW
โ€”
not yet in upstream
VIR risk
7.5

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.

Predictions

Exploit likelihood
83%
Patch ETA
โ€”

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No mitigations published for this CVE yet.

The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or โ€” if you've already worked around this in production โ€” publish your fix to the community-verified tier.

โœš Propose a mitigation on Community โ†’ Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here with source_tier=community-verified.

OS impact

OSVersionStatusFixed in
debian debianbookwormfixed1.0.5-1
debian debianbullseyefixed1.0.5-1
debian debianforkyfixed1.0.5-1
debian debiansidfixed1.0.5-1
debian debiantrixiefixed1.0.5-1

Package impact

EcosystemPackageVulnerableFixed
golang Gogopkg.in/square/go-jose.v1<1.1.01.1.0

Application impact

VendorProductVersionsFixed
go-jose_projectgo-jose{"endIncluding":"1.0.3"}

References

CWEs

CWE-284

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.