CVE-2022-31671
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 user permissions when reading and updating job execution logs through the P2P preheat execution logs. By sending a request that attempts to read/update P2P preheat execution logs and specifying different job IDs, malicious authenticated users could read all the job logs stored in the Harbor database.
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 confidenceHarbor lacks proper authorization checks when reading/updating P2P preheat job execution logs. Authenticated users can access arbitrary job logs by manipulating job IDs in requests, allowing unauthorized disclosure of all job logs stored in the database.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L
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 versionCheck the installed Harbor version via the web UI (under 'Harbor Version' in the footer) or by querying the API at /api/v2.0/systeminfoAffected if Version is >= 2.0.0 and < 2.4.3, OR >= 2.5.0 and < 2.5.2
-
Determine if P2P preheat is configuredCheck if any P2P preheat policies exist. In the Harbor web UI, navigate to 'Projects' > select a project > 'P2P Preheat' tab, or query the API at /api/v2.0/p2p/preheat/policiesAffected if P2P preheat policies are present and Harbor version is in the affected range
-
Review API access logs for job log endpointExamine API access logs for requests to endpoints like /api/v2.0/p2p/preheat/jobs/*/logs that may indicate unauthorized access to job logsAffected if Logs show job log access with job IDs that the requesting user did not create
-
Check for anomalous job log access patternsAudit API logs for requests to /api/v2.0/p2p/preheat/jobs/{job_id}/logs where the job_id does not correspond to the user's projectsAffected if Multiple job IDs are being accessed by users who should not have access to those specific jobs
If Harbor version falls within 2.0.0-2.4.3 or 2.5.0-2.5.2 AND P2P preheat is in use, the environment is potentially affected by unauthorized job log disclosure via ID manipulation.
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 proper permission validation to ensure users can only access job logs for jobs they own or are authorized to view. Consider adding role-based access control checks before returning job execution data.
Harbor 2.4.3 or later (2.4.x branch), or 2.5.2 or later (2.5.x branch), or latest stable release (2.6+/2.7+)
- 1. Identify the currently installed Harbor version by checking the Harbor portal or Helm values
- 2. For Harbor installations >= 2.0.0 and < 2.4.3: Plan upgrade to version 2.4.3 or later (preferably latest 2.4.x stable)
- 3. For Harbor installations >= 2.5.0 and < 2.5.2: Plan upgrade to version 2.5.2 or later (preferably latest 2.5.x stable)
- 4. For Harbor installations on 2.6.x or later: Verify current version includes the security fix; if uncertain, upgrade to the latest stable release
- 5. Before upgrading, backup the Harbor database and configuration
- 6. Follow the official Harbor upgrade guide for your deployment method (Helm chart or manual)
- 7. After upgrade, verify that P2P preheat functionality still works correctly
- 8. Test that users can only access their own job execution logs, not logs from other jobs
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31671 — 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-31671 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