CVE-2020-29662
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIn Harbor 2.0 before 2.0.5 and 2.1.x before 2.1.2, the container registry's catalog API endpoint is exposed on an unauthenticated path, allowing unauthenticated users to query the image catalog and potentially enumerate available container images and tags.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2.0, < 2.0.5>= 2.1.0, < 2.1.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Harbor versionRun 'harbor -v' or check the Harbor UI footer version, or query the /api/systeminfo endpointAffected if Installed version is >= 2.0.0 and < 2.0.5, or >= 2.1.0 and < 2.1.2
-
Confirm Harbor is internet-facing or accessible externallyReview network configuration, firewall rules, or load balancer settings that expose Harbor ports (80, 443) to untrusted networksAffected if The Harbor registry is reachable from untrusted networks without network-level access controls
-
Test unauthenticated catalog API accessSend a GET request to /v2/_catalog without any authentication headers using curl or a browser: curl -s http://<harbor-host>/v2/_catalogAffected if The request returns a JSON response containing repository names without requiring authentication
-
Check for proxy or gateway authentication enforcementReview any reverse proxy (nginx, traefik, etc.) or API gateway configuration in front of Harbor to see if /v2/_catalog routes are explicitly protectedAffected if No authentication is required at the proxy layer for the catalog endpoint
You are affected if Harbor version is 2.0.0-2.0.4 or 2.1.0-2.1.1 AND the /v2/_catalog endpoint is reachable without authentication from an untrusted network.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data2.0.52.1.2
Upgrade Harbor to version 2.0.5, 2.1.2, or later to enforce authentication on the registry catalog API. Alternatively, configure network-level access controls to restrict the affected endpoint.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-29662 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-29662 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data