Cross-project access via unchecked namespace transfer
Published Dec 12, 2023 · Updated Aug 4, 2024
Incorrect authorization in SUSE Rancher 2.6.0 through 2.6.12 and 2.7.0 through 2.7.3 allows remote authenticated users to access other projects. The namespace-move path checks source-namespace update privileges without verifying access to the destination project, then preserves the mover's former permissions after transfer. Project Owner, Project Member, or equivalent custom-role access to the source project is required; successful abuse exposes project secrets and can consume the destination project's quota.
Summary
What happened
Incorrect authorization in SUSE Rancher 2.6.0 through 2.6.12 and 2.7.0 through 2.7.3 allows remote authenticated users to access other projects. The namespace-move path checks source-namespace update privileges without verifying access to the destination project, then preserves the mover's former permissions after transfer. Project Owner, Project Member, or equivalent custom-role access to the source project is required; successful abuse exposes project secrets and can consume the destination project's quota.
The record
- CVE
- CVE-2020-10676
- Published
- Dec 12, 2023
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-863, T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 12, 2023CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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