Skip to content

Harbor fails to validate the user permissions when updating tag immutability policies

Moderate severity GitHub Reviewed Published Aug 29, 2022 in goharbor/harbor • Updated Nov 19, 2024

Package

gomod github.com/goharbor/harbor (Go)

Affected versions

>= 1.0.0, <= 1.10.12
>= 2.0.0, <= 2.4.2
>= 2.5.0, <= 2.5.1

Patched versions

1.10.13
2.4.3
2.5.2

Description

Impact

Harbor fails to validate the user permissions when updating tag immutability policies - API call:

PUT /projects/{project_name_or_id}/immutabletagrules/{immutable_rule_id}

By sending a request to update a tag immutability policy with an id that belongs to a
project that the currently authenticated user doesn’t have access to, the attacker could
modify tag immutability 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:

Credits

Thanks to Gal Goldstein and Daniel Abeles from Oxeye Security for reporting this issue.

References

@qnetter qnetter published to goharbor/harbor Aug 29, 2022
Published to the GitHub Advisory Database Sep 16, 2022
Reviewed Sep 16, 2022
Published by the National Vulnerability Database Nov 14, 2024
Last updated Nov 19, 2024

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
Low
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:L

EPSS score

0.046%
(17th percentile)

Weaknesses

CVE ID

CVE-2022-31669

GHSA ID

GHSA-8c6p-v837-77f6

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.