Cross-tenant repository disclosure and deletion via unscoped query
Published Mar 6, 2024 · Updated Aug 2, 2024
Improper authorization in Stacklok Minder before 0.0.33 allows remote authenticated users to read or delete other tenants' repositories. GetRepositoryByRepoName filters only by provider, owner, and repository name, omitting the caller's project ID from the database lookup. Any authenticated user with a configured provider can supply another tenant's owner and repository name to obtain repository details or delete its database record.
Summary
What happened
Improper authorization in Stacklok Minder before 0.0.33 allows remote authenticated users to read or delete other tenants' repositories. GetRepositoryByRepoName filters only by provider, owner, and repository name, omitting the caller's project ID from the database lookup. Any authenticated user with a configured provider can supply another tenant's owner and repository name to obtain repository details or delete its database record.
The record
- CVE
- CVE-2024-27916
- Published
- Mar 6, 2024
- Updated
- Aug 2, 2024
- Vendor
- Stacklok
- Product
- Minder
- Classifications
- CWE-285, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 6, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 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=0 <0.0.33
- Affected versionversion=< 0.0.33
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Public exploit references
- GHSA-v627-69v2-xx37 command-line proof of conceptproof of concept · demonstrated
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