dbcve.org
HarborApplication · Linuxfoundation

CVE-2022-31669

HIGH · 7.7 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 →
83/100
Remediation priority · High
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 the user permissions when updating tag immutability policies.  By sending a request to update a tag immutability policy with an id that belongs to a project that the currently authenticated user doesn’t have access to, the attacker could modify tag immutability 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 updating tag immutability policies, allowing an authenticated attacker to modify tag immutability policies in projects they don't have access to by manipulating the project ID in the API request. This is an Insecure Direct Object Reference (IDOR) authorization bypass vulnerability.

MitigationApply the vendor-provided patch/upgrade to the fixed Harbor version. Until patched, implement additional access control validation at the API gateway layer or monitor for unauthorized tag immutability policy modifications across projects.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/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. Check installed Harbor version
    Run 'harbor -v' or check the Harbor UI under the ' Harbor version' field in the about page, or query the API endpoint /api/v2.0/systeminfo
    Affected if Installed version falls within 2.0.0 to <2.4.3 or 2.5.0 to <2.5.2
  2. Identify if tag immutability policies are configured
    Query the Harbor API endpoint GET /api/v2.0/projects/{project_id}/immutabletagrules or navigate to each project in the UI under 'Tag Immutability' settings
    Affected if Any project has tag immutability rules defined - the vulnerability enables unauthorized modification of these rules
  3. Review audit logs for tag immutability policy changes
    Check Harbor audit logs (accessible via UI under 'Logs' or via the API /api/v2.0/logs) for entries with action 'update-immutable-tag' - compare the acting user's project permissions against the project_id in each log entry
    Affected if Log entries show immutability policy modifications on projects where the acting user does not have project administrator or higher privileges
  4. Inspect API access logs for anomalous project ID manipulation
    Review API gateway or Harbor access logs for POST/PUT requests to /api/v2.0/projects/*/immutabletagrules where the project ID in the URL differs from projects the authenticated user is authorized to access
    Affected if API requests target immutability endpoints with project IDs outside the user's authorized projects

You are affected if your Harbor version is 2.0.0 through <2.4.3 or 2.5.0 through <2.5.2 AND you have tag immutability policies configured, with evidence of unauthorized modifications or suspicious API calls manipulating project IDs.

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

Apply the vendor-provided patch/upgrade to the fixed Harbor version. Until patched, implement additional access control validation at the API gateway layer or monitor for unauthorized tag immutability policy modifications across projects.

Recommended fix High confidence

Upgrade to Harbor 2.4.3 (if on 2.0.x-2.4.x) or Harbor 2.5.2 (if on 2.5.x)

  1. 1. Identify the currently running Harbor version using the Harbor web interface or API
  2. 2. If running version 2.0.0 through 2.4.2, plan upgrade to version 2.4.3
  3. 3. If running version 2.5.0 or 2.5.1, plan upgrade to version 2.5.2
  4. 4. Review Harbor upgrade documentation for your deployment method (helm, operator, or direct installation)
  5. 5. Backup Harbor database and configuration before upgrading
  6. 6. Perform the upgrade following the official Harbor upgrade guide
  7. 7. After upgrade, verify the Harbor instance is operational
  8. 8. Test that tag immutability policies can only be modified by users with appropriate project permissions
Caveat Review Harbor release notes for any breaking changes between your current version and the target version before upgrading

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

Fix this in Harbor Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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