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.

Sign up for GitHub

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

Jump to bottom

x/vuln/osv: advisory URL should be in top-level database_specific field #57033

Closed
tatianab opened this issue Dec 1, 2022 · 2 comments
Closed

x/vuln/osv: advisory URL should be in top-level database_specific field #57033

tatianab opened this issue Dec 1, 2022 · 2 comments
Assignees
@tatianab
Labels
FrozenDueToAge vulncheck or vulndb Issues for the x/vuln or x/vulndb repo
Milestone
vuln/unplanned

Comments

@tatianab
Copy link

tatianab commented Dec 1, 2022

Currently, the Go advisory URL is published under affected.database_specific.url in OSV. It should instead be published under the top-level database_specific.url field, because it applies to the whole vulnerability.
@tatianab tatianab added the vulncheck or vulndb Issues for the x/vuln or x/vulndb repo label Dec 1, 2022
@gopherbot gopherbot modified the milestones: Unreleased, vuln/unplanned Dec 1, 2022
@tatianab tatianab self-assigned this Dec 1, 2022
@gopherbot
Copy link

Change https://go.dev/cl/454556 mentions this issue: osv: add top-level DatabaseSpecific field

@gopherbot
Copy link

Change https://go.dev/cl/454558 mentions this issue: internal/database: move URL to top-level database_specific field

@julieqiu julieqiu changed the title x/vuln: advisory URL should be in top-level database_specific field x/vuln/osv: advisory URL should be in top-level database_specific field Dec 22, 2022
@tatianab tatianab closed this as completed Apr 4, 2023
@golang golang locked and limited conversation to collaborators Apr 3, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@tatianab tatianab

Labels
FrozenDueToAge vulncheck or vulndb Issues for the x/vuln or x/vulndb repo
Projects
None yet
Milestone
vuln/unplanned
Development

No branches or pull requests
2 participants
@tatianab @gopherbot