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-38r5-34mr-mvm7 #1307

Closed
GoVulnBot opened this issue Jan 9, 2023 · 1 comment

Comments

@GoVulnBot
Copy link

In GitHub Security Advisory GHSA-38r5-34mr-mvm7, there is a vulnerability in the following Go packages or modules:

Unit Fixed Vulnerable Ranges
github.com/goharbor/harbor 2.1.2 >= 2.1.0, < 2.1.2

Cross references:

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

modules:
  - module: TODO
    versions:
      - introduced: 2.1.0
        fixed: 2.1.2
    packages:
      - package: github.com/goharbor/harbor
  - module: TODO
    versions:
      - fixed: 2.0.5
    packages:
      - package: github.com/goharbor/harbor
description: |-
    ### **Impact**
    Javier Provecho, member of the TCCT (Telefonica Cloud & Cybersecurity Tech better known as ElevenPaths) SRE team discovered a vulnerability regarding Harbor’s v2 API.

    The catalog’s registry v2 api is exposed on an unauthenticated path. The current catalog API path is served at the following path and it requires to be authenticated as an admin.

    "GET /v2/_catalog"

    However, the authorization can be bypassed by using the following path

    "GET /v2/_catalog/"

    ### **Patches**
    If your product uses the affected releases of Harbor, update to either version v2.1.2 or v2.0.5 to fix this issue immediately

    https://github.com/goharbor/harbor/releases/tag/v2.1.2
    https://github.com/goharbor/harbor/releases/tag/v2.0.5

    ### **Workarounds**
    If you cannot access a patched release, it can be mitigated by disabling that API. For example, redirecting it to a 404 sink hole in the ingress.

    ### **For more information**
    If you have any questions or comments about this advisory, contact [email protected]
    View our security policy at https://github.com/goharbor/harbor/security/policy
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-29662
cves:
  - CVE-2020-29662
ghsas:
  - GHSA-38r5-34mr-mvm7

@tatianab
Copy link
Contributor

tatianab commented Jan 9, 2023

Duplicate of #785

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants