User permission validation failure and disclosure of P2P preheat execution logs
Harbor
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/goharbor/harbor Go |
|
|
Harbor
| Product | Affected | Fixed in |
|---|---|---|
| github.com/goharbor/harbor Go |
|
|
| github.com/goharbor/harbor/src Go |
|
|
Harbor fails to validate the user permissions when updating p2p preheat policies. By sending a request to update a p2p preheat policy with an id that belongs to a project that the currently authenticated user doesn't have access to, the attacker could modify p2p preheat policies configured in other projects.
From the CVE record · vmware
Harbor does not check project permissions when a user updates a p2p preheat policy. An authenticated attacker can send an update request using a policy ID from a project they cannot access and modify that project's policy.
Teams running Harbor or the Go packages github.com/goharbor/harbor (2.0.0 to before 2.4.3, or 2.5.0 to before 2.5.2, including the corresponding +incompatible versions) and github.com/goharbor/harbor/src (before 0.0.0-20220630175814-b4ef1db) should check their versions.