CVE-2022-31667
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 a robot account that belongs to a project that the authenticated user doesn’t have access to. By sending a request that attempts to update a robot account, and specifying a robot account id and robot account name that belongs to a different project that the user doesn’t have access to, it was possible to revoke the robot account permissions.
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 fails to validate user permissions when updating robot accounts. An authenticated user can send a request to update a robot account by specifying a robot account ID and name belonging to a different project they don't have access to, successfully revoking that robot account's permissions without proper authorization.
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
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/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 Harbor installation version via the UI under 'Harbor Version' in the administration section, or query the API endpoint /api/v2.0/systeminfo, or run 'harbor -v' if CLI is availableAffected if The installed version falls within >= 2.0.0 and < 2.4.3, or >= 2.5.0 and < 2.5.2
-
Review audit logs for robot account modificationsAccess Harbor's audit logs via the UI under 'Logs' or the API /api/v2.0/logs. Search for operations on robot accounts where the requesting user is not a member of the target projectAffected if Audit entries show robot account updates performed by users who lack permissions for the project owning the robot account
-
Inspect API access logs for unauthorized robot account operationsCheck Harbor's underlying logs (typically in /var/log/harbor/ or via Docker logs if deployed containerized) for PUT/PATCH requests to /api/v2.0/robots/ with project IDs the requesting user is not authorized to accessAffected if API requests show robot account modifications targeting projects outside the user's project memberships
-
Verify robot account ownership consistencyList all robot accounts via /api/v2.0/robots and cross-reference the project_id field with the user's actual project memberships. Identify any robot accounts that were modified by users not listed as project admins or developers for that projectAffected if Robot account modification records exist where the modifying user has no role in the target project
A Harbor instance is affected if it runs version 2.0.0 through 2.4.2, or 2.5.0 through 2.5.1, AND audit/API logs show robot account modifications performed by users without project access.
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
Apply vendor patches for CVE-2022-31667. Until then, restrict API access to trusted users and monitor for unauthorized robot account modifications.
2.4.3 or later (for 2.0.0-2.4.x users); 2.5.2 or later (for 2.5.x users)
- Identify the current Harbor version by checking the Harbor UI or running `harbor -v`
- If running Harbor 2.0.0 - 2.4.x, upgrade to version 2.4.3 or later
- If running Harbor 2.5.0 - 2.5.1, upgrade to version 2.5.2 or later
- Follow the standard Harbor upgrade documentation for your deployment method (Docker Compose or Kubernetes)
- After upgrade, verify that the authorization check is properly enforced by confirming users can no longer modify robot accounts in projects they don't have access to
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31667 — 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-31667 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