dbcve.org
HarborApplication · Linuxfoundation

CVE-2022-46463

HIGH · 7.5 CVSS v3.1 Published 2023-01-13
Fix available
A fix is available. Upgrade to after 2.5.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
An access control issue in Harbor v1.X.X to v2.5.3 allows attackers to access public and private image repositories without authentication. NOTE: the vendor's position is that this "is clearly described in the documentation as a feature."

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 · moderate confidence

Harbor container registry versions 1.X.X through 2.5.3 contain an access control bypass where attackers can access both public and private image repositories without any authentication. This allows unauthenticated enumeration and retrieval of container images that were intended to be private.

MitigationImplement network-level access controls to restrict exposure of the Harbor registry, or upgrade to a version beyond 2.5.3 if a patch is available. Review and enforce proper authentication policies for all repository access.

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
HarborApplication
Affected:>= 1.1.0, <= 2.5.3

CVSS 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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Harbor version
    Check the running Harbor version via the Harbor UI admin panel under 'Harbor Version' or by querying the API endpoint /api/v2.0/systeminfo, or inspect the docker images or helm release for the Harbor version tag
    Affected if The installed version falls within >= 1.1.0 and <= 2.5.3
  2. Verify API accessibility without credentials
    Send an HTTP request to the Harbor API endpoint for a private project without providing any authentication headers (for example, GET /api/v2.0/projects/<private_project_name>/repositories)
    Affected if The API returns successful responses with repository data from private projects without authentication
  3. Test registry pull access anonymously
    Attempt to pull a container image from a private repository using docker without logging in (docker pull <harbor-host>/<private-project>/<image>:<tag>)
    Affected if The pull succeeds without requiring docker login authentication
  4. Inspect project access settings
    Review Harbor project settings in the UI or via API to confirm which projects are marked as private and verify that the 'anonymous' user does not have explicit read permissions
    Affected if Private projects are accessible to unauthenticated users despite configuration settings

You are affected if Harbor version is between 1.1.0 and 2.5.3 AND the registry allows unauthenticated access to private project repositories or images.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 2.5.3
Interim mitigation

Implement network-level access controls to restrict exposure of the Harbor registry, or upgrade to a version beyond 2.5.3 if a patch is available. Review and enforce proper authentication policies for all repository access.

Recommended fix Moderate confidence

Harbor 2.7.0 or latest stable release

  1. 1. Identify your current Harbor installation version by checking the Harbor dashboard or running 'harbor -v'
  2. 2. Backup your Harbor database and configuration files before upgrading
  3. 3. Upgrade Harbor to version 2.6.0 or later (2.7.0 recommended for latest stable release)
  4. 4. After upgrade, verify that authentication is properly enforced for private repository access
  5. 5. Test that unauthenticated access to private repositories is no longer possible
Caveat Review Harbor 2.6.x and 2.7.x release notes for any breaking changes related to authentication, API changes, or migration requirements before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Harbor Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-46463 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-46463 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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