Policy remediation bypass via mismatched repository identifiers
Published Feb 26, 2024 · Updated Aug 27, 2024
Improper input validation in Stacklok Minder before 0.20240226.1425+ref.53868a8 allows remote authenticated users to disrupt policy remediation. RegisterRepository accepts an owner, repository name, and repo_id without verifying that they identify the same upstream repository before storing data and registering webhooks. Exploitation requires provider administration of the named repository and leaves conflicting policy changes without reconciliation or remediation.
Summary
What happened
Improper input validation in Stacklok Minder before 0.20240226.1425+ref.53868a8 allows remote authenticated users to disrupt policy remediation. RegisterRepository accepts an owner, repository name, and repo_id without verifying that they identify the same upstream repository before storing data and registering webhooks. Exploitation requires provider administration of the named repository and leaves conflicting policy changes without reconciliation or remediation.
The record
- CVE
- CVE-2024-27093
- Published
- Feb 26, 2024
- Updated
- Aug 27, 2024
- Vendor
- Stacklok
- Product
- Minder
- Classifications
- CWE-20, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 2024CVE publishedPublication date reported by the CVE source.
- Aug 27, 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.20240226.1425\+ref.53868a8
- Affected versionversion=< 0.20240226.1425+ref.53868a8
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.
Public exploit references
- GHSA-q6h8-4j2v-pjg4 RPC 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