First published: Fri Sep 16 2022(Updated: )
### Impact Harbor fails to validate the user permissions when updating tag retention policies. API call: PUT /retentions/{id} By sending a request to update a tag retention policy with an id that belongs to a project that the currently authenticated user doesn’t have access to, the attacker could modify tag retention policies configured in other projects. ### 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 | >=1.0.0<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-31670 has been classified with a moderate severity due to improper validation of user permissions.
To remediate CVE-2022-31670, update Harbor to version 2.5.2, 2.4.3, or 1.10.13 or later.
CVE-2022-31670 affects Harbor versions from 2.0.0 to 2.5.1, and 1.0.0 to 1.10.12.
Yes, CVE-2022-31670 can lead to unauthorized access as it allows users to update tag retention policies without proper permission checks.
CVE-2022-31670 impacts the API endpoint for updating tag retention policies in Harbor.