First published: Fri Sep 16 2022(Updated: )
### Impact Harbor fails to validate the user permissions to view Webhook policies including relevant credentials configured in different projects the user doesn’t have access to, resulting in malicious users being able to read Webhook policies of other users/projects. API call is GET /projects/{project_name_or_id}/webhook/policies/{webhook_policy_id} By sending the below request and specifying different Webhook policy ids in the last part of the URL, the malicious user may disclose Webhook policies related to other repositories/projects.: none;"> ### Patches This and similar issues are fixed in Harbor v2.5.2 and later. Please upgrade as soon as possible. ### 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](https://github.com/goharbor/harbor) ### Credits Thanks to [Gal Goldstein](https://www.linkedin.com/in/gal-goldshtein/) and [Daniel Abeles](https://www.linkedin.com/in/daniel-abeles/) from [Oxeye Security](https://www.oxeye.io/) for reporting this issue.
Credit: security@vmware.com security@vmware.com
Affected Software | Affected Version | How to fix |
---|---|---|
go/github.com/goharbor/harbor | >=2.5.0<=2.5.1 | 2.5.2 |
go/github.com/goharbor/harbor | >=2.0.0<=2.4.2 | 2.4.3 |
go/github.com/goharbor/harbor | >=1.0.0<=1.10.12 | 1.10.13 |
Harbor | >=2.0.0<2.4.3 | |
Harbor | >=2.5.0<2.5.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-31666 is classified as a high severity vulnerability due to improper permission validation allowing unauthorized access to sensitive Webhook policies.
To resolve CVE-2022-31666, upgrade to Harbor versions 2.5.2, 2.4.3, or 1.10.13, which contain the necessary security patches.
CVE-2022-31666 affects all Harbor projects that leverage Webhook policies without proper user permission validation.
Users of Harbor versions 2.5.0 to 2.5.1, 2.0.0 to 2.4.2, and 1.0.0 to 1.10.12 are at risk for CVE-2022-31666.
CVE-2022-31666 enables attackers to read and potentially manipulate Webhook policies configured by other users in various projects.