vulndb/data/excluded/GO-2022-0331.yaml

id: GO-2022-0331
excluded: NOT_GO_CODE
modules:
    - module: github.com/envoyproxy/envoy
cves:
    - CVE-2021-43825
ghsas:
    - GHSA-h69p-g6xg-mhhh
data: add lint check for ID and add ID to all YAML reports Adds the ID field to all YAML reports and adds a lint check to enforce that all reports have the correct value for the field. Also adds a step to "vulnreport fix" to fix the ID if needed. Change-Id: I51f4654e127528e1dbbfcb9c59da3658ad52098b Reviewed-on: https://go-review.googlesource.com/c/vulndb/+/498281 Run-TryBot: Tatiana Bradley <tatianabradley@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Damien Neil <dneil@google.com> 2023-05-24 21:02:12 +03:00			`id: GO-2022-0331`
data/excluded: create entries for excluded reports Change-Id: I49b44a49eba4332601aaae38a2ce70ee2f9ba399 Reviewed-on: https://go-review.googlesource.com/c/vulndb/+/423494 Run-TryBot: Damien Neil <dneil@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Julie Qiu <julieqiu@google.com> 2022-08-13 02:03:53 +03:00			`excluded: NOT_GO_CODE`
internal/report, cmd/vulnreport, data/excluded: require excluded reports to have module information. Modify report.Lint() so that it requires all excluded report (aside from Not Go Code) to also have module information. Also modifies createExcluded to be more robust against malformed and unreachable module paths in github issue titles. This (in addition to go/dev/cl/446868) allows us to add some module information to every report. Ideally, this will allow us to check if anyone is importing the modules mentioned in the excluded reports for our metrics. Change-Id: I783aea978760a70a0cccd30ad454d1fadfb85997 Reviewed-on: https://go-review.googlesource.com/c/vulndb/+/448837 Run-TryBot: Maceo Thompson <maceothompson@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Tatiana Bradley <tatiana@golang.org> 2022-11-08 23:15:12 +03:00			`modules:`
data: fix whitespace in all YAML reports Change-Id: Ie2503c1c8b0bc714dbe8c66a27de7d448c77dce8 Reviewed-on: https://go-review.googlesource.com/c/vulndb/+/499657 Run-TryBot: Tatiana Bradley <tatianabradley@google.com> Reviewed-by: Julie Qiu <julieqiu@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> 2023-06-01 00:04:08 +03:00			`- module: github.com/envoyproxy/envoy`
data/excluded: create entries for excluded reports Change-Id: I49b44a49eba4332601aaae38a2ce70ee2f9ba399 Reviewed-on: https://go-review.googlesource.com/c/vulndb/+/423494 Run-TryBot: Damien Neil <dneil@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Julie Qiu <julieqiu@google.com> 2022-08-13 02:03:53 +03:00			`cves:`
data: fix whitespace in all YAML reports Change-Id: Ie2503c1c8b0bc714dbe8c66a27de7d448c77dce8 Reviewed-on: https://go-review.googlesource.com/c/vulndb/+/499657 Run-TryBot: Tatiana Bradley <tatianabradley@google.com> Reviewed-by: Julie Qiu <julieqiu@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> 2023-06-01 00:04:08 +03:00			`- CVE-2021-43825`
data/excluded: add missing/related aliases for excluded reports Quite a few missing aliases were found via the osv.dev API. In many cases, these are derived from GHSAs which have a "repo-level" advisory but not a "global-level" advisory, and are therefore not accessible via the Github GraphQL API. The osv.dev database in some cases considers two IDs to be aliases which we would consider only "related". A best-effort attempt was made to distinguish between false-positives (which were placed in the "related" section), and true positives. Change-Id: Ic418d8f6cf40658098e56eafafcc44434dae0ebd Reviewed-on: https://go-review.googlesource.com/c/vulndb/+/581715 LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Auto-Submit: Tatiana Bradley <tatianabradley@google.com> Reviewed-by: Damien Neil <dneil@google.com> 2024-04-25 00:09:05 +03:00			`ghsas:`
			`- GHSA-h69p-g6xg-mhhh`