CVE-2016-9121

Name: CVE-2016-9121
Creator: NVD / NIST
Published: 2017-03-28T02:59:00.213+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

UnknownEPSS 1.41%

Last modified Jun 17, 2026

CVE-2016-9121 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 1.41% chance of exploitation in the next 30 days.

Description

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.

Metrics

EPSS Probability

1.41%

69.2th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-326

Affected Software

Vendor	Product	Versions
Go-Jose Project	Go-Jose	<= 1.0.3

References

http://www.openwall.com/lists/oss-security/2016/11/03/1Mailing List, Patch, Third Party Advisory
https://github.com/square/go-jose/commit/c7581939a3656bb65e89d64da0a52364a33d2507Issue Tracking, Patch, Third Party Advisory
https://hackerone.com/reports/164590Permissions Required
http://www.openwall.com/lists/oss-security/2016/11/03/1Mailing List, Patch, Third Party Advisory
https://github.com/square/go-jose/commit/c7581939a3656bb65e89d64da0a52364a33d2507Issue Tracking, Patch, Third Party Advisory
https://hackerone.com/reports/164590Permissions Required

Timeline

Published: Mar 28, 2017
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2016-9121?

How severe is CVE-2016-9121?

Severity scoring for CVE-2016-9121 is pending analysis. The EPSS model estimates a 1.41% probability of exploitation in the next 30 days.

How do I fix CVE-2016-9121?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2016-9121?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST