Cross-project policy modification via missing authorization
Published Nov 14, 2024 · Updated Nov 14, 2024
Incorrect authorization in Harbor allows remote authenticated users to alter tag retention policies for inaccessible projects. The PUT /retentions/{id} handler accepts a policy identifier without verifying that its project is accessible to the caller. Any authenticated account able to reach the API can modify another project's retention configuration; no data-reading or code-execution impact is reported.
Summary
What happened
Incorrect authorization in Harbor allows remote authenticated users to alter tag retention policies for inaccessible projects. The PUT /retentions/{id} handler accepts a policy identifier without verifying that its project is accessible to the caller. Any authenticated account able to reach the API can modify another project's retention configuration; no data-reading or code-execution impact is reported.
The record
- CVE
- CVE-2022-31670
- Published
- Nov 14, 2024
- Updated
- Nov 14, 2024
- Vendor
- Cloud Native Computing Foundation
- Product
- Harbor
- Classifications
- CWE-285, CWE-863, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 14, 2024CVE publishedPublication date reported by the CVE source.
- Nov 14, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Harbor (Go) 2.x<=2.4.2; 2.5<=2.5.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo