Skip to content
Fencer Intel
high 7.5

CVE-2015-9258 json

Docker Notary Signature Algorithm Not Matched to Key vulnerability

published 2018-03-31 8 y ago modified 2026-06-17 4 mo ago also GHSA-785h-hrf7-gqxc , EUVD-2022-2949

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 63%
public exploits
0
none known

Summary

In Docker Notary before 0.1, gotuf/signed/verify.go has a Signature Algorithm Not Matched to Key vulnerability. Because an attacker controls the field specifying the signature algorithm, they might (for example) be able to forge a signature by forcing a misinterpretation of an RSA-PSS key as Ed25519 elliptic-curve data.

Patch / fix

  • go github.com/docker/notary 0.1.0
  • docker notary 0.1
  • notary Debian 13, Debian 12 0.1~ds1-1

debian advisories DEBIAN-CVE-2015-9258

Exploit prediction

1.03% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N
GitHub 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
go github.com/docker/notary
<0.1.0
0.1.0

Classification

Weakness
  • CWE-310 Cryptographic Issues
  • CWE-347 Improper Verification of Cryptographic Signature

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.