{"answers":{"affected":"2 open source packages ship an affected version, including github.com/docker/notary. It affects 1 product.","exploited":"There is no known exploitation of CVE-2015-9258 in the wild and no public exploit code.","fix":"Upgrade github.com/docker/notary to 0.1.0 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2015-9258 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2015-9258 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/docker/notary (Go): affected all versions; fixed in 0.1.0\n- github.com/docker/notary (Go): affected all versions; fixed in 0.1.0\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2015-9258/ (Markdown: https://insights.sbomify.com/CVE-2015-9258/index.md)","id":"CVE-2015-9258","markdown":"https://insights.sbomify.com/CVE-2015-9258/index.md","name":"CVE-2015-9258","record":{"aliases":["DEBIAN-CVE-2015-9258","GHSA-785h-hrf7-gqxc"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Docker Notary library","requires_auth":"none","summary":"Attackers can forge signatures by exploiting signature algorithm mismatches in Docker Notary, bypassing integrity checks.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"notary","vendor":"docker"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-310","name":null}],"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.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Docker Notary Signature Algorithm Not Matched to Key vulnerability","id":"CVE-2015-9258","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"other","year":"2015"},"n_packages":2,"n_references":2,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2015-9259"},"packages":[{"ecosystem":"Go","fixed":["0.1.0"],"introduced":["0"],"last_affected":[],"package":"github.com/docker/notary","purl":null,"source":"GHSA-785h-hrf7-gqxc"},{"ecosystem":"Go","fixed":["0.1.0"],"introduced":["0"],"last_affected":[],"package":"github.com/docker/notary","purl":"pkg:golang/github.com/docker/notary","source":"GHSA-785h-hrf7-gqxc"}],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2015-9257"},"products":["n/a"],"published":"2018-03-31","related":[{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2015-9259","kev_date_added":null,"published":"2018-03-31"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Attackers can forge signatures by exploiting signature algorithm mismatches in Docker Notary, bypassing integrity checks.","url":"https://insights.sbomify.com/CVE-2015-9258/"}