Every CVE Search/ Get API key

CVE-2022-31670

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

7.7 HighFix available

Harbor fails to validate the user permissions when updating tag retention policies. 

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.

Attack profile

How easy it is to exploit

Attack vector
Network
Complexity
Low
Privileges needed
Low
User interaction
None

What an attacker can affect

Confidentiality
None
Integrity
High
Availability
None

Exploit likelihood

0.55%Up 0.5 points since Nov 15, 2024
90%50%10%1%

What each source reports

CVE List Score used 7.7

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

Harbor fails to validate the user permissions when updating tag retention policies. 

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.

Record
CVE-2022-31670
CVSS 3.1
7.7 HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N
Weakness
CWE-285
Updated
2026-11-02
EUVDEUVD-2022-6672 7.7

Harbor fails to validate the user permissions when updating tag retention policies. 

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.

Record
EUVD-2022-6672
CVSS 3.1
7.7 HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N
Updated
2026-11-03
GitHub AdvisoriesGHSA-3637-v6vq-xqqw 7.7

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

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:

Credits

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

Record
GHSA-3637-v6vq-xqqw
CVSS 3.1
7.7 HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N
Weakness
CWE-285, CWE-863
Updated
2026-11-02
NVD 7.7

Harbor fails to validate the user permissions when updating tag retention policies. 

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.

Record
CVE-2022-31670
CVSS 3.1
7.7 HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N
Weakness
CWE-285, CWE-863
Updated
2026-11-02
OSV 7.7

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

Harbor fails to validate the user permissions when updating tag retention policies. 

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.

Record
CVE-2022-31670
CVSS 3.1
7.7 HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N
Weakness
CWE-285
Updated
2026-11-02
OSVGHSA-3637-v6vq-xqqw 7.7

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

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:

Credits

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

Record
GHSA-3637-v6vq-xqqw
CVSS 3.1
7.7 HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N
Weakness
CWE-285, CWE-863
Updated
2026-11-02
OSVBIT-harbor-2022-31670 No score

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

Harbor fails to validate the user permissions when updating tag retention policies. 

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.

Record
BIT-harbor-2022-31670
Updated
2026-11-02

Affected products

Affected packages

Affected packages
PackageAffectedFixed
github.com/goharbor/harbor
Go
1.0.0 to 1.10.12
1.10.13
github.com/goharbor/harbor
Go
2.0.0 to 2.4.2
2.4.3
github.com/goharbor/harbor
Go
2.5.0 to 2.5.1
2.5.2
harbor
Bitnami
1.0.0 up to 1.10.13, 2.0.0 up to 2.4.3, 2.5.0 up to 2.5.2
1.10.132.4.32.5.2
github.com/goharbor/harbor
Go
1.0.0 up to 1.10.13
1.10.13
github.com/goharbor/harbor
Go
2.0.0 up to 2.4.3
2.4.3
github.com/goharbor/harbor
Go
2.5.0 up to 2.5.2
2.5.2

History

History
RecordedChangedSources
aliases, productsEUVD
first indexedCVE List, GitHub Advisories, NVD, OSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

CVE-2022-31670 is a high vulnerability (CVSS 7.7) in Harbor, published September 16, 2022. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.55%, the 45th percentile. Fixed in github.com/goharbor/harbor 1.10.13.

References

MoveEnter Open