-
Notifications
You must be signed in to change notification settings - Fork 61
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/v6: GHSA-7ggc-5r84-xf54 #540
Labels
excluded: EFFECTIVELY_PRIVATE
This vulnerability exists in a package can be imported, but isn't meant to be outside that module.
Comments
Vuln in tool. |
neild
added
excluded: EFFECTIVELY_PRIVATE
This vulnerability exists in a package can be imported, but isn't meant to be outside that module.
and removed
NotGoVuln
NeedsTriage
labels
Aug 10, 2022
This was referenced Aug 11, 2023
x/vulndb: potential Go vuln in github.com/mattermost/mattermost-server/v6: GHSA-6xjj-v76v-fwpj
#2007
Closed
x/vulndb: potential Go vuln in github.com/mattermost/mattermost-server/v6: GHSA-9rww-66w7-7vjx
#2008
Closed
x/vulndb: potential Go vuln in github.com/mattermost/mattermost-server/v6: GHSA-g3v6-r8p9-wxg9
#2009
Closed
This was referenced Sep 30, 2023
x/vulndb: potential Go vuln in github.com/mattermost/mattermost-server/v6: GHSA-33r7-wjfc-7w98
#2087
Closed
x/vulndb: potential Go vuln in github.com/mattermost/mattermost-server/v6: GHSA-9hwp-cj7m-wjw4
#2089
Closed
x/vulndb: potential Go vuln in github.com/mattermost/mattermost-server/v6: GHSA-h69v-mvh9-hfrq
#2090
Closed
x/vulndb: potential Go vuln in github.com/mattermost/mattermost-server/v6: GHSA-h8wh-f7gw-fwpr
#2091
Closed
This was referenced Nov 28, 2023
x/vulndb: potential Go vuln in github.com/mattermost/mattermost-server/v6: GHSA-3487-3j7c-7gwj
#2358
Closed
x/vulndb: potential Go vuln in github.com/mattermost/mattermost-server/v6: GHSA-4ghx-8jw8-p76q
#2359
Closed
x/vulndb: potential Go vuln in github.com/mattermost/mattermost-server/v6: GHSA-85jj-c9jr-9jhx
#2360
Closed
x/vulndb: potential Go vuln in github.com/mattermost/mattermost-server/v6: GHSA-c37r-v8jx-7cv2
#2361
Closed
x/vulndb: potential Go vuln in github.com/mattermost/mattermost-server/v6: GHSA-j4c3-3h73-74m9
#2362
Closed
Change https://go.dev/cl/592768 mentions this issue: |
This was referenced Aug 2, 2024
x/vulndb: potential Go vuln in github.com/mattermost/mattermost/server/v8: GHSA-762m-4cx6-6mf4
#3020
Closed
x/vulndb: potential Go vuln in github.com/mattermost/mattermost/server/v8: GHSA-9fpw-c9x7-cv3j
#3022
Closed
x/vulndb: potential Go vuln in github.com/mattermost/mattermost/server/v8: GHSA-vg67-chm7-8m3j
#3023
Closed
x/vulndb: potential Go vuln in github.com/mattermost/mattermost/server/v8: GHSA-vg6q-84p8-qvqh
#3024
Closed
x/vulndb: potential Go vuln in github.com/mattermost/mattermost/server/v8: GHSA-56mc-f9w7-2wxq
#3025
Closed
x/vulndb: potential Go vuln in github.com/mattermost/mattermost/server/v8: GHSA-cmc8-222c-vqp9
#3028
Closed
x/vulndb: potential Go vuln in github.com/mattermost/mattermost/server/v8: GHSA-jq3g-xqpx-37x3
#3030
Closed
x/vulndb: potential Go vuln in github.com/mattermost/mattermost/server/v8: GHSA-jr9x-3x7m-4j75
#3031
Closed
Change https://go.dev/cl/607220 mentions this issue: |
gopherbot
pushed a commit
that referenced
this issue
Aug 21, 2024
- data/reports/GO-2022-0507.yaml - data/reports/GO-2022-0508.yaml - data/reports/GO-2022-0509.yaml - data/reports/GO-2022-0510.yaml - data/reports/GO-2022-0511.yaml - data/reports/GO-2022-0512.yaml - data/reports/GO-2022-0516.yaml - data/reports/GO-2022-0517.yaml - data/reports/GO-2022-0518.yaml - data/reports/GO-2022-0540.yaml - data/reports/GO-2022-0547.yaml - data/reports/GO-2022-0550.yaml - data/reports/GO-2022-0554.yaml - data/reports/GO-2022-0556.yaml - data/reports/GO-2022-0559.yaml - data/reports/GO-2022-0560.yaml - data/reports/GO-2022-0561.yaml - data/reports/GO-2022-0562.yaml - data/reports/GO-2022-0566.yaml - data/reports/GO-2022-0570.yaml Updates #507 Updates #508 Updates #509 Updates #510 Updates #511 Updates #512 Updates #516 Updates #517 Updates #518 Updates #540 Updates #547 Updates #550 Updates #554 Updates #556 Updates #559 Updates #560 Updates #561 Updates #562 Updates #566 Updates #570 Change-Id: I3197ea86e01d2ed4ae9e7f17dbd7a3e495c903e4 Reviewed-on: https://go-review.googlesource.com/c/vulndb/+/607220 Reviewed-by: Damien Neil <[email protected]> Auto-Submit: Tatiana Bradley <[email protected]> LUCI-TryBot-Result: Go LUCI <[email protected]>
This was referenced Aug 22, 2024
x/vulndb: potential Go vuln in github.com/mattermost/mattermost/server/v8: GHSA-2jhx-w3vc-w59g
#3089
Closed
x/vulndb: potential Go vuln in github.com/mattermost/mattermost/server/v8: GHSA-3j95-8g47-fpwh
#3090
Closed
x/vulndb: potential Go vuln in github.com/mattermost/mattermost/server/v8: GHSA-fxq9-6946-34q7
#3091
Closed
x/vulndb: potential Go vuln in github.com/mattermost/mattermost/server/v8: GHSA-q22q-2rrf-m27p
#3092
Closed
x/vulndb: potential Go vuln in github.com/mattermost/mattermost/server/v8: GHSA-4ww8-fprq-cq34
#3093
Closed
x/vulndb: potential Go vuln in github.com/mattermost/mattermost/server/v8: GHSA-5263-pm2h-m7hw
#3094
Closed
x/vulndb: potential Go vuln in github.com/mattermost/mattermost/server/v8: GHSA-c6vp-jjgv-38wj
#3096
Closed
This was referenced Oct 28, 2024
x/vulndb: potential Go vuln in github.com/mattermost/mattermost/server/v8: GHSA-hm57-h27x-599c
#3227
Closed
x/vulndb: potential Go vuln in github.com/mattermost/mattermost/server/v8: GHSA-6mvp-gh77-7vwh
#3232
Closed
x/vulndb: potential Go vuln in github.com/mattermost/mattermost/server/v8: GHSA-762g-9p7f-mrww
#3233
Closed
x/vulndb: potential Go vuln in github.com/mattermost/mattermost/server/v8: GHSA-762v-rq7q-ff97
#3234
Closed
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-7ggc-5r84-xf54, there is a vulnerability in the following Go packages or modules:
See doc/triage.md for instructions on how to triage this report.
The text was updated successfully, but these errors were encountered: