CVE-2020-29662: GO-2022-0785 - "catalog's registry v2 api exposed on unauthenticated path in Harbor" in github.com/goharbor/harbor

CVE-2020-29662 · Severity: low · CVSS 3.1 · Published 2024-08-21

"catalog's registry v2 api exposed on unauthenticated path in Harbor" in github.com/goharbor/harbor

Technologies: github.com/goharbor/harbor (Go). Vendors: Go.

Quick answers

Is CVE-2020-29662 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2020-29662 being exploited in the wild.
How severe is CVE-2020-29662?
Low severity, with a CVSS score of 3.1, published 21 August 2024.
Which products and versions are affected?
github.com/goharbor/harbor (Go) SEMVER:introduced=0,fixed=2.0.5, SEMVER:introduced=0,fixed=2.0.5+incompatible,introduced=2.1.0+incompatible,fixed=2.1.2+incompatible.
Is there a fix for CVE-2020-29662?
Yes. github.com/goharbor/harbor (Go): upgrade to 2.0.5, 2.1.2+incompatible or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2020-29662?
Check whether you run github.com/goharbor/harbor (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/goharbor/harbor (Go): upgrade to 2.0.5, 2.1.2+incompatible or later
    go get github.com/goharbor/harbor@v2.1.2+incompatible

Affected products

  • github.com/goharbor/harbor (Go) SEMVER:introduced=0,fixed=2.0.5, SEMVER:introduced=0,fixed=2.0.5+incompatible,introduced=2.1.0+incompatible,fixed=2.1.2+incompatible

Identifiers

  • CVE-2020-29662
  • GHSA-38r5-34mr-mvm7
  • GO-2022-0785

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.