First published: Fri Sep 16 2022(Updated: )
### Impact 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: 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. ### 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 |
Linuxfoundation Harbor | >=2.0.0<2.4.3 | |
Linuxfoundation 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.