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.

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/rancher/rancher: GHSA-xh8x-j8h3-m5ph #2784

Closed
GoVulnBot opened this issue Apr 25, 2024 · 2 comments
Assignees
Labels

Comments

@GoVulnBot
Copy link

In GitHub Security Advisory GHSA-xh8x-j8h3-m5ph, there is a vulnerability in the following Go packages or modules:

Unit Fixed Vulnerable Ranges
github.com/rancher/rancher 2.2.2 >= 2.2.0, < 2.2.2

Cross references:

See doc/triage.md for instructions on how to triage this report.

modules:
    - module: github.com/rancher/rancher
      versions:
        - introduced: 2.2.0
          fixed: 2.2.2
      packages:
        - package: github.com/rancher/rancher
    - module: github.com/rancher/rancher
      versions:
        - introduced: TODO (earliest fixed "", vuln range ">= 2.1.0, <= 2.1.8")
      packages:
        - package: github.com/rancher/rancher
    - module: github.com/rancher/rancher
      versions:
        - introduced: TODO (earliest fixed "", vuln range ">= 2.0.0, <= 2.0.13")
      packages:
        - package: github.com/rancher/rancher
summary: Rancher Recreates Default User With Known Password Despite Deletion in github.com/rancher/rancher
cves:
    - CVE-2019-11202
ghsas:
    - GHSA-xh8x-j8h3-m5ph
references:
    - web: https://nvd.nist.gov/vuln/detail/CVE-2019-11202
    - web: https://forums.rancher.com/t/rancher-release-v2-2-2-addresses-rancher-cve-2019-11202-and-stability-issues/13977
    - advisory: https://github.com/advisories/GHSA-xh8x-j8h3-m5ph
source:
    id: GHSA-xh8x-j8h3-m5ph

@gopherbot
Copy link
Contributor

Change https://go.dev/cl/591202 mentions this issue: data/reports: add 9 unreviewed reports

@gopherbot
Copy link
Contributor

Change https://go.dev/cl/607456 mentions this issue: data/reports: update 6 reports

gopherbot pushed a commit that referenced this issue Aug 21, 2024
Fix reports which won't pass an upcoming lint check
by merging / collapsing their version ranges.

  - data/reports/GO-2022-0617.yaml
  - data/reports/GO-2023-1573.yaml
  - data/reports/GO-2023-1574.yaml
  - data/reports/GO-2023-1730.yaml
  - data/reports/GO-2023-1946.yaml
  - data/reports/GO-2024-2784.yaml

Updates #617
Updates #1573
Updates #1574
Updates #1730
Updates #1946
Updates #2784

Change-Id: If02308deccab77b00cf10cb3619263e456d1ea64
Reviewed-on: https://go-review.googlesource.com/c/vulndb/+/607456
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants