CVE-2022-31668
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 · uneditedHarbor fails to validate the user permissions when updating p2p preheat policies. By sending a request to update a p2p preheat policy with an id that belongs to a project that the currently authenticated user doesn't have access to, the attacker could modify p2p preheat 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 confidenceHarbor lacks authorization checks when updating p2p preheat policies, allowing authenticated users to modify policies in projects they don't have access to by manipulating the policy ID in the request. This is an Insecure Direct Object Reference (IDOR) vulnerability resulting in unauthorized cross-project resource modification.
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.0, < 2.4.3>= 2.5.0, < 2.5.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Harbor installation versionQuery the Harbor API systeminfo endpoint: GET /api/v2.0/systeminfo, or inspect the harbor.yml configuration file, or run 'docker ps' if deployed via containers to locate the harbor-core container and check its versionAffected if The installed version falls within >= 2.0.0 and < 2.4.3, or >= 2.5.0 and < 2.5.2
-
Verify p2p preheat feature is in useCheck if p2p preheat policies exist by querying the API: GET /api/v2.0/p2pPreheatPolicies, or inspect the harbor.yml configuration file for p2p_preheat configuration sectionAffected if P2p preheat policies are configured and accessible in the Harbor instance
-
Check authorization on policy update endpointAttempt a controlled test: as an authenticated user without project access, send a PUT request to /api/v2.0/p2pPreheatPolicies/{policy_id} with a policy ID from a project the user cannot access, and verify whether the request succeeds or is rejected with 403 ForbiddenAffected if The update request succeeds when it should fail, indicating the IDOR vulnerability allows cross-project modification
The environment is affected if Harbor version is in the vulnerable ranges AND p2p preheat policies exist AND the policy update API allows modification of policies in projects where the user lacks permissions.
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.
dbcve · scoped2.4.32.5.2
Implement project-level permission validation in the p2p preheat policy update endpoint to ensure users can only modify policies within projects they have explicit access to.
Harbor 2.4.3 (or later 2.x stable release)
- 1. Identify the currently installed Harbor version using `harbor -v` or checking the deployment configuration
- 2. For Harbor versions >= 2.0.0 and < 2.4.3: Plan upgrade to version 2.4.3 or later
- 3. For Harbor versions >= 2.5.0 and < 2.5.2: Plan upgrade to version 2.5.2 or later
- 4. Before upgrading, backup the Harbor database and configuration files
- 5. Follow the official Harbor upgrade guide for your deployment method (docker-compose or Kubernetes Helm)
- 6. Run database migrations if required by the upgrade
- 7. Verify the upgrade was successful by checking the Harbor UI and API accessibility
- 8. Test that authorization controls are properly enforced on p2p preheat policy operations
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31668 — 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-2022-31668 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