CVE-2020-29662 "catalog's registry v2 api exposed on unauthenticated path in Harbor"

Medium 5.3 Published Updated

Unauthenticated access to the catalog registry API allows attackers to read sensitive registry data in Harbor.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2020-29662?

CVE-2020-29662 is a medium-severity missing authorization vulnerability in n/a, published on 2 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

In Harbor 2.0 before 2.0.5 and 2.1.x before 2.1.2 the catalog’s registry API is exposed on an unauthenticated path.

Weakness: CWE-319

Which versions are affected by CVE-2020-29662?

6 open source packages ship an affected version, including github.com/goharbor/harbor and harbor. It affects 1 product.

PackageAffectedFixed in
github.com/goharbor/harbor GoAll versions2.0.5+incompatible, 2.1.2+incompatible
github.com/goharbor/harbor GoAll versions2.0.5
github.com/goharbor/harbor GoAll versions2.0.5
github.com/goharbor/harbor GoFrom 2.1.02.1.2
github.com/goharbor/harbor GoFrom 2.1.02.1.2
harbor BitnamiFrom 2.0.02.0.5, 2.1.2

Products include Linuxfoundation Harbor.

How do I fix CVE-2020-29662?

Upgrade github.com/goharbor/harbor to a fixed version for your release line: 2.0.5+incompatible, 2.1.2+incompatible, 2.0.5 or 2.1.2.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2020-29662 being exploited?

There is no known exploitation of CVE-2020-29662 in the wild and no public exploit code.

Sources

Also known as BIT-harbor-2020-29662, GHSA-38r5-34mr-mvm7, GO-2022-0785.

Is CVE-2020-29662 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free