CVE-2024-22278: Harbor fails to validate the user permissions when updating project configurations
Impact Harbor fails to validate the maintainer role permissions when creating/updating/deleting project configurations - API call: - PUT /projects/{projectnameorid}/metadatas/{metaname} - POST /projects/{projectnameorid}/metadatas/{metaname} - DELETE /projects/{projectnameorid}/metadatas/{metaname} By sending a request to create/update/delete a metadata with an name that belongs to a project that the currently…
Published Jul 31, 2024 · Updated Nov 18, 2024
Affected packages
github.com/goharbor/harbor
- Ecosystem
- Go
- Affected
- < 2.9.5
- Fixed in
- 2.9.5
- Check
go list -m github.com/goharbor/harbor
github.com/goharbor/harbor
- Ecosystem
- Go
- Affected
- >= 2.10.0, < 2.10.3
- Fixed in
- 2.10.3
- Check
go list -m github.com/goharbor/harbor
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
Harbor fails to validate the maintainer role permissions when creating/updating/deleting project configurations - API call:
- PUT /projects/{project_name_or_id}/metadatas/{meta_name}
- POST /projects/{project_name_or_id}/metadatas/{meta_name}
- DELETE /projects/{project_name_or_id}/metadatas/{meta_name}
By sending a request to create/update/delete a metadata with an name that belongs to a project that the currently authenticated and granted to the maintainer role user doesn’t have access to, the attacker could modify configurations in the current project.
BTW: the maintainer role in Harbor was intended for individuals who closely support the project admin in maintaining the project but lack configuration management permissions. However, the maintainer role can utilize the metadata API to circumvent this limitation. It's important to note that any potential attacker must be authenticated and granted a specific project maintainer role to modify configurations, limiting their scope to only that project.
Patches
Will be fixed in v2.9.5, v2.10.3 and v2.11.0
Workarounds
There are no workarounds available.
Credit
Thanks to Ravid Mazon([email protected]), Jay Chen ([email protected]) Palo Alto Networks for reporting this issue.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesGHSA-prh4-vhfh-24mj
Harbor: LDAP password and OIDC secret are not redacted in the audit log
medium6.9Mar 26, 2026CVE-2026-4404
Harbor allows the use of the default password for web UI login
critical9.4No fixMar 23, 2026CVE-2025-30086
Possible ORM Leak Vulnerability in the Harbor
medium4.9Jul 23, 2025CVE-2025-32019
Harbor repository description page has Cross-site Scripting vulnerability
medium4.1No fixJul 23, 2025CVE-2022-31668
Harbor fails to validate the user permissions when updating p2p preheat policies
high7.4Nov 14, 2024CVE-2024-22244
Open Redirect URL in Harbor
medium4.3Jun 2, 2024
