# CVE-2015-9258: Docker Notary Signature Algorithm Not Matched to Key vulnerability

> Attackers can forge signatures by exploiting signature algorithm mismatches in Docker Notary, bypassing integrity checks.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Mar 2018
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-9258, GHSA-785h-hrf7-gqxc

## What is CVE-2015-9258?

CVE-2015-9258 is a high-severity vulnerability in n/a, published on 31 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-310

## Which versions are affected by CVE-2015-9258?

2 open source packages ship an affected version, including github.com/docker/notary. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/docker/notary` | Go | All versions | 0.1.0 |
| `github.com/docker/notary` | Go | All versions | 0.1.0 |

Products: Docker Notary.

## How do I fix CVE-2015-9258?

Upgrade github.com/docker/notary to 0.1.0 or later.

## Is CVE-2015-9258 being exploited?

There is no known exploitation of CVE-2015-9258 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2015-9259](https://insights.sbomify.com/CVE-2015-9259/): Security feature bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-9258 and fix it if it is affected.

What it is: CVE-2015-9258 is a high-severity vulnerability in n/a, published on 31 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-9258 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/docker/notary (Go): affected all versions; fixed in 0.1.0
- github.com/docker/notary (Go): affected all versions; fixed in 0.1.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2015-9258/ (Markdown: https://insights.sbomify.com/CVE-2015-9258/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2015-9258
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-9258
- OSV: https://osv.dev/vulnerability/CVE-2015-9258

---
From sbomify Insights: https://insights.sbomify.com/CVE-2015-9258/
Summaries are generated and may contain mistakes; the official description above is the record.