You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See doc/triage.md for instructions on how to triage this report.
modules:
- module: github.com/goharbor/harbor
versions:
- introduced: TODO (earliest fixed "2.5.2", vuln range ">= 2.5, <= 2.5.1")
packages:
- package: github.com/goharbor/harbor
- module: github.com/goharbor/harbor
versions:
- introduced: TODO (earliest fixed "2.4.3", vuln range ">= 2.0, <= 2.4.2")
packages:
- package: github.com/goharbor/harbor
- module: github.com/goharbor/harbor
versions:
- introduced: TODO (earliest fixed "1.10.13", vuln range ">= 1.0, <= 1.10.12")
packages:
- package: github.com/goharbor/harbor
description: |
### 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.
cves:
- CVE-2022-31670
ghsas:
- GHSA-3637-v6vq-xqqw
The text was updated successfully, but these errors were encountered:
In GitHub Security Advisory GHSA-3637-v6vq-xqqw, there is a vulnerability in the following Go packages or modules:
Cross references:
See doc/triage.md for instructions on how to triage this report.
The text was updated successfully, but these errors were encountered: