dbcve.org
HarborApplication · Linuxfoundation

CVE-2022-31666

MEDIUM · 5.4 CVSS v3.1 Published 2024-11-14
Fix available
A fix is available. Upgrade to 2.4.3 / 2.5.2 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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
Harbor fails to validate user permissions while deleting Webhook policies, allowing malicious users to view, update and delete Webhook policies of other users.  The attacker could modify Webhook policies configured in other projects.

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 confidence

Harbor fails to validate user permissions when performing operations on Webhook policies, allowing authenticated malicious users to view, update, and delete Webhook policies belonging to other users or projects. This is a Broken Access Control (IDOR) vulnerability where the application does not verify the requesting user has authorization to modify the targeted webhook policy.

MitigationImplement proper authorization checks in Harbor's webhook policy API endpoints to verify the requesting user has sufficient permissions (project admin or appropriate role) for the target project before allowing view, update, or delete operations on Webhook policies.

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:>= 2.0.0, < 2.4.3>= 2.5.0, < 2.5.2

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 installed Harbor version
    Access the Harbor administration UI, go to 'Harbor Admiral' or check /api/version endpoint, or run 'helm list' if deployed via Helm
    Affected if Installed version falls within >= 2.0.0 and < 2.4.3, or >= 2.0.0 and < 2.4.3, or >= 2.5.0 and < 2.5.2
  2. Determine if Webhook feature is in use
    Navigate to a project's 'Webhooks' settings via the UI, or query the Harbor API at /api/projects/{project_id}/webhook/policies
    Affected if Webhook policies exist in any project (vulnerability only applies if webhooks are configured)
  3. Audit API access logs for webhook policy operations
    Review Harbor logs for GET/PUT/DELETE requests to /api/projects/*/webhook/policies endpoints, checking for access patterns where users accessed webhook policies outside their own project
    Affected if Logs show webhook policy API calls from users to policies in projects they do not belong to
  4. Check for multiple projects or shared webhook configurations
    List all projects in Harbor and identify any webhook policies configured, noting which users have access to each
    Affected if Multiple projects exist with webhook policies and users have varying project-level roles (conditions needed for IDOR exploitation)
  5. Verify authorization behavior on webhook policy APIs
    Using a low-privilege user account belonging to Project A, attempt to query, modify, or delete webhook policies belonging to Project B via the REST API
    Affected if User can successfully perform operations on webhook policies belonging to a different project without proper authorization errors

User is affected if running a Harbor version in the vulnerable range AND webhook policies are configured, and especially if testing confirms unauthorized cross-project webhook policy access is possible.

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 2.4.3 / 2.5.2 or later
Fixed in 2.4.32.5.2
Interim mitigation

Implement proper authorization checks in Harbor's webhook policy API endpoints to verify the requesting user has sufficient permissions (project admin or appropriate role) for the target project before allowing view, update, or delete operations on Webhook policies.

Recommended fix High confidence

Upgrade to Harbor 2.4.3 or 2.5.2 (or latest stable 2.x release)

  1. 1. Back up the current Harbor installation including database and storage
  2. 2. Download the fixed Harbor version (2.4.3 or 2.5.2) from the official Harbor releases
  3. 3. Stop the currently running Harbor services
  4. 4. Run the Harbor upgrade script (./install.sh or upgrade.sh depending on installation method)
  5. 5. Verify the upgrade was successful by checking Harbor UI and API access
  6. 6. Confirm webhook policy permissions are now properly enforced by testing cross-user webhook operations
Caveat Review Harbor release notes for any breaking changes between your current version and the target version; database migrations may be required

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

Fix this in Harbor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-31666 — 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-31666 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