Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

x/vulndb: potential Go vuln in github.com/docker/notary: GHSA-785h-hrf7-gqxc #1994

Closed
GoVulnBot opened this issue Aug 2, 2023 · 2 comments
Closed
Assignees
Labels
excluded: EFFECTIVELY_PRIVATE This vulnerability exists in a package can be imported, but isn't meant to be outside that module.

Comments

@GoVulnBot
Copy link

In GitHub Security Advisory GHSA-785h-hrf7-gqxc, there is a vulnerability in the following Go packages or modules:

Unit Fixed Vulnerable Ranges
github.com/docker/notary 0.1.0 < 0.1.0

Cross references:
No existing reports found with this module or alias.

See doc/triage.md for instructions on how to triage this report.

modules:
    - module: github.com/docker/notary
      versions:
        - fixed: 0.1.0
      packages:
        - package: github.com/docker/notary
summary: Docker Notary Signature Algorithm Not Matched to Key vulnerability
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.
cves:
    - CVE-2015-9258
ghsas:
    - GHSA-785h-hrf7-gqxc
references:
    - web: https://nvd.nist.gov/vuln/detail/CVE-2015-9258
    - web: https://github.com/theupdateframework/notary/blob/master/docs/resources/ncc_docker_notary_audit_2015_07_31.pdf
    - web: https://web.archive.org/web/20160305015752/https://docs.docker.com/notary/changelog/
    - advisory: https://github.com/advisories/GHSA-785h-hrf7-gqxc

@tatianab tatianab self-assigned this Aug 3, 2023
@tatianab tatianab added the excluded: EFFECTIVELY_PRIVATE This vulnerability exists in a package can be imported, but isn't meant to be outside that module. label Aug 4, 2023
@gopherbot
Copy link
Contributor

Change https://go.dev/cl/516055 mentions this issue: data/excluded: batch add 10 excluded reports

@gopherbot
Copy link
Contributor

Change https://go.dev/cl/592762 mentions this issue: data/reports: unexclude 75 reports

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
excluded: EFFECTIVELY_PRIVATE This vulnerability exists in a package can be imported, but isn't meant to be outside that module.
Projects
None yet
Development

No branches or pull requests

3 participants