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/goharbor/harbor: GHSA-q9x4-q76f-5h5j #704

Closed
GoVulnBot opened this issue Aug 1, 2022 · 3 comments
Assignees
Labels
excluded: EFFECTIVELY_PRIVATE This vulnerability exists in a package can be imported, but isn't meant to be outside that module.

Comments

@GoVulnBot
Copy link

In GitHub Security Advisory GHSA-q9x4-q76f-5h5j, there is a vulnerability in the following Go packages or modules:

Unit Fixed Vulnerable Ranges
github.com/goharbor/harbor 2.0.1 >= 2.0.0, < 2.0.1

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

packages:
  - package: github.com/goharbor/harbor
    versions:
      - introduced: 2.0.0
        fixed: 2.0.1
  - package: github.com/goharbor/harbor
    versions:
      - introduced: 1.7.0
        fixed: 1.10.3
description: "# Impact\nSean Wright from Secureworks has discovered an enumeration
    vulnerability. An attacker can make use of the Harbor API to make unauthenticated
    calls to the Harbor instance. Based on the HTTP status code in the response, an
    attacker is then able to work out which resources exist, and which do not. This
    would likely be accomplished by either providing a wordlist or enumerating through
    a sequence an\nunauthenticated attacker is able to enumerate resources on the
    system. This provides them with information such as existing projects, repositories,
    etc.\n\nThe vulnerability was immediately fixed by the Harbor team.  \n\n# Issue
    \nThe following API resources where found to be vulnerable to enumeration attacks:\n/api/chartrepo/{repo}/prov
    (POST)\n/api/chartrepo/{repo}/charts (GET, POST)\n/api/chartrepo/{repo}/charts/{name}
    (GET, DELETE)\n/api/chartrepo/{repo}/charts/{name}/{version} (GET, DELETE)\n/api/labels?name={name}&scope=p
    (GET)\n/api/repositories?project_id={id} (GET)\n/api/repositories/{repo_name}/
    (GET, PUT, DELETE)\n/api/repositories/{repo_name}/tags (GET)\n/api/repositories/{repo_name}/tags/{tag}/manifest?version={version}
    (GET)\n/api/repositories/{repo_name/{tag}/labels (GET)\n/api/projects?project_name={name}
    (HEAD)\n/api/projects/{project_id}/summary (GET)\n/api/projects/{project_id}/logs
    (GET)\n/api/projects/{project_id} (GET, PUT, DELETE)\n/api/projects/{project_id}/metadatas
    (GET, POST)\n/api/projects/{project_id}/metadatas/{metadata_name} (GET, PUT)\n\n#
    Known Attack Vectors\nSuccessful exploitation of this issue will lead to bad actors
    identifying which resources exist in Harbor without requiring authentication for
    the Harbor API.\n\n# Patches\nIf your product uses the affected releases of Harbor,
    update to version 1.10.3 or 2.0.1 to patch this issue immediately.\n\nhttps://github.com/goharbor/harbor/releases/tag/v1.10.3\nhttps://github.com/goharbor/harbor/releases/tag/v2.0.1\n\n#
    Workarounds\nThere is no known workaround\n\n# For more information\nIf you have
    any questions or comments about this advisory, contact cncf-harbor-security@lists.cncf.io\nView
    our security policy at https://github.com/goharbor/harbor/security/policy"
published: 2022-02-11T23:17:25Z
last_modified: 2022-02-11T23:17:25Z
cves:
  - CVE-2019-19030
ghsas:
  - GHSA-q9x4-q76f-5h5j
links:
    context:
      - https://github.com/advisories/GHSA-q9x4-q76f-5h5j

@neild
Copy link
Contributor

neild commented Aug 9, 2022

Vulnerability in tool.

@gopherbot
Copy link
Contributor

Change https://go.dev/cl/592770 mentions this issue: data/reports: unexclude 50 reports

@gopherbot
Copy link
Contributor

Change https://go.dev/cl/607223 mentions this issue: data/reports: unexclude 20 reports (21)

gopherbot pushed a commit that referenced this issue Aug 21, 2024
  - data/reports/GO-2022-0642.yaml
  - data/reports/GO-2022-0644.yaml
  - data/reports/GO-2022-0645.yaml
  - data/reports/GO-2022-0647.yaml
  - data/reports/GO-2022-0649.yaml
  - data/reports/GO-2022-0700.yaml
  - data/reports/GO-2022-0703.yaml
  - data/reports/GO-2022-0704.yaml
  - data/reports/GO-2022-0705.yaml
  - data/reports/GO-2022-0707.yaml
  - data/reports/GO-2022-0708.yaml
  - data/reports/GO-2022-0709.yaml
  - data/reports/GO-2022-0732.yaml
  - data/reports/GO-2022-0749.yaml
  - data/reports/GO-2022-0751.yaml
  - data/reports/GO-2022-0752.yaml
  - data/reports/GO-2022-0759.yaml
  - data/reports/GO-2022-0760.yaml
  - data/reports/GO-2022-0769.yaml
  - data/reports/GO-2022-0770.yaml

Updates #642
Updates #644
Updates #645
Updates #647
Updates #649
Updates #700
Updates #703
Updates #704
Updates #705
Updates #707
Updates #708
Updates #709
Updates #732
Updates #749
Updates #751
Updates #752
Updates #759
Updates #760
Updates #769
Updates #770

Change-Id: I3dabcc907fd498009a9bd4cf865198037615717e
Reviewed-on: https://go-review.googlesource.com/c/vulndb/+/607223
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
excluded: EFFECTIVELY_PRIVATE This vulnerability exists in a package can be imported, but isn't meant to be outside that module.
Projects
None yet
Development

No branches or pull requests

3 participants