We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In GitHub Security Advisory GHSA-6r7x-4q7g-h83j, there is a vulnerability in the following Go packages or modules:
Cross references:
See doc/triage.md for instructions on how to triage this report.
modules: - module: github.com/rancher/rancher versions: - introduced: TODO (earliest fixed "2.1.6", vuln range ">= 2.0.0, <= 2.1.5") packages: - package: github.com/rancher/rancher summary: |- Rancher Project Members Have Continued Access to Namespaces After Being Removed From Them in github.com/rancher/rancher cves: - CVE-2019-6287 ghsas: - GHSA-6r7x-4q7g-h83j references: - web: https://nvd.nist.gov/vuln/detail/CVE-2019-6287 - report: https://github.com/rancher/rancher/issues/17244 - report: https://github.com/rancher/rancher/issues/17724 - web: https://forums.rancher.com/t/rancher-release-v2-1-6/13148 - web: https://forums.rancher.com/t/rancher-security-announcement-cve-2018-20321-and-cve-2019-6287/13149 - web: https://rancher.com/blog/2019/2019-01-29-explaining-security-vulnerabilities-addressed-in-rancher-v2-1-6-and-v2-0-11 - advisory: https://github.com/advisories/GHSA-6r7x-4q7g-h83j source: id: GHSA-6r7x-4q7g-h83j
The text was updated successfully, but these errors were encountered:
Change https://go.dev/cl/590278 mentions this issue: data/reports: add 48 unreviewed reports
data/reports: add 48 unreviewed reports
Sorry, something went wrong.
8ed6db9
maceonthompson
No branches or pull requests
In GitHub Security Advisory GHSA-6r7x-4q7g-h83j, there is a vulnerability in the following Go packages or modules:
Cross references:
See doc/triage.md for instructions on how to triage this report.
The text was updated successfully, but these errors were encountered: