Go Jose All Versions Before 1.0.4
Approved changes feed: RSS · Atom
cpe:2.3:a:n/a:go_jose_all_versions_before_1.0.4:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | N/A (22f567d3-1203-528c-8f0e-3eb9c2f6ca78) |
|---|---|
| Product | Go Jose All Versions Before 1.0.4 (e3ddf763-0ba8-5b37-a78d-de6c932826f6) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2016-9122 |
vulnerable | 2026-06-08 05:08:22.615122 |
Details available
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.
Published: 2017-03-28T02:46:00.000Z
Updated: 2024-08-06T02:42:10.637Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2016-9121 |
vulnerable | 2026-06-08 05:08:22.613882 |
Details available
go-jose before 1.0.4 suffers from an invalid curve attack for the ECDH-ES algorithm. When deriving a shared key using ECDH-ES for an encrypted message, go-jose neglected to check that the received public key on a message is on the same curve as the static private key of the receiver, thus making it vulnerable to an invalid curve attack.
Published: 2017-03-28T02:46:00.000Z
Updated: 2024-08-06T02:42:10.399Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.