-
Notifications
You must be signed in to change notification settings - Fork 62
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/mattermost/mattermost/server/v8: GHSA-r67m-mf7v-qp7j #2182
Labels
excluded: EFFECTIVELY_PRIVATE
This vulnerability exists in a package can be imported, but isn't meant to be outside that module.
Comments
Vulnerability in tool. No packages seem to be imported. |
zpavlinovic
added
the
excluded: EFFECTIVELY_PRIVATE
This vulnerability exists in a package can be imported, but isn't meant to be outside that module.
label
Nov 8, 2023
tatianab
removed
the
excluded: EFFECTIVELY_PRIVATE
This vulnerability exists in a package can be imported, but isn't meant to be outside that module.
label
Nov 8, 2023
zpavlinovic
added
the
excluded: EFFECTIVELY_PRIVATE
This vulnerability exists in a package can be imported, but isn't meant to be outside that module.
label
Nov 8, 2023
Change https://go.dev/cl/540875 mentions this issue: |
This was referenced Jan 3, 2024
This was referenced Feb 29, 2024
This was referenced Apr 5, 2024
Change https://go.dev/cl/592763 mentions this issue: |
This was referenced Aug 2, 2024
This was referenced Aug 2, 2024
This was referenced Aug 22, 2024
This was referenced Oct 28, 2024
This was referenced Dec 13, 2024
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.
In GitHub Security Advisory GHSA-r67m-mf7v-qp7j, there is a vulnerability in the following Go packages or modules:
Cross references:
No existing reports found with this module or alias.
See doc/triage.md for instructions on how to triage this report.
The text was updated successfully, but these errors were encountered: