CVE-2022-31667

PUT /robots/{robot_id}

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.

Workarounds

There are no workarounds available.

For more information

If you have any questions or comments about this advisory:

• Open an issue in the Harbor GitHub repository

Credits

Thanks to Gal Goldstein and Daniel Abeles from Oxeye Security for reporting this issue.

Harbor 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. API call:

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

CVE-2022-31667 has a CVSS score of 6.4 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.10.13, 2.4.3, 2.5.2); upgrading removes the vulnerable code path.

Kodem intelligence

This and similar issues are fixed in Harbor v2.5.2 and later. Please upgrade as soon as possible.

1. What is CVE-2022-31667? CVE-2022-31667 is a medium-severity incorrect authorization vulnerability in github.com/goharbor/harbor (go), affecting versions >= 1.0.0, <= 1.10.12. It is fixed in 1.10.13, 2.4.3, 2.5.2. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. How severe is CVE-2022-31667? CVE-2022-31667 has a CVSS score of 6.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/goharbor/harbor are affected by CVE-2022-31667? github.com/goharbor/harbor (go) versions >= 1.0.0, <= 1.10.12 is affected.
4. Is there a fix for CVE-2022-31667? Yes. CVE-2022-31667 is fixed in 1.10.13, 2.4.3, 2.5.2. Upgrade to this version or later.
5. Is CVE-2022-31667 exploitable, and should I be worried? Whether CVE-2022-31667 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-31667 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-31667?
   • Upgrade github.com/goharbor/harbor to 1.10.13 or later
   • Upgrade github.com/goharbor/harbor to 2.4.3 or later
   • Upgrade github.com/goharbor/harbor to 2.5.2 or later