https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 07:48:41 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-9516 EUVD-2026-9516 https://cve.radiocsirt.org/vuln/euvd-2026-9516 https://cve.radiocsirt.org/vuln/fkie_cve-2024-27916 <p>Minder is a software supply chain security platform. Prior to version 0.0.33, a Minder user can use the endpoints `GetRepositoryByName`, `DeleteRepositoryByName`, and `GetArtifactByName` to access any repository in the database, irrespective of who owns the repo and any permissions present. The database query checks by repo owner, repo name and provider name (which is always `github`). These query values are not distinct for the particular user - as long as the user has valid credentials and a provider, they can set the repo owner/name to any value they want and the server will return information on this repo. Version 0.0.33 contains a patch for this issue.</p> <p>Minder is a software supply chain security platform. Prior to version 0.0.33, a Minder user can use the endpoints `GetRepositoryByName`, `DeleteRepositoryByName`, and `GetArtifactByName` to access any repository in the database, irrespective of who owns the repo and any permissions present. The database query checks by repo owner, repo name and provider name (which is always `github`). These query values are not distinct for the particular user - as long as the user has valid credentials and a provider, they can set the repo owner/name to any value they want and the server will return information on this repo. Version 0.0.33 contains a patch for this issue.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-27916 https://cve.radiocsirt.org/vuln/ghsa-v627-69v2-xx37 <p><strong>Affected:</strong> Go: github.com/stacklok/minder</p> <p>### Summary A Minder user can use the endpoints listed in the issue title to access any repository in the DB, irrespective of who owns the repo and any permissions that user may have. ### Details</p> <p>https://github.com/stacklok/minder/blob/e88e4b286e4bc04c03b0332a77961f085e1aa77f/database/query/repositories.sql#L22-L23 https://github.com/stacklok/minder/blob/a115c8524fbd582b2b277eaadce024bebbded508/internal/controlplane/handlers_repositories.go#L277-L278</p> <p>The DB query used here checks by repo owner, repo name and provider name (which is always &#34;github&#34;). These query values are not distinct for the particular user - as long as the user has valid credentials and a provider, they can set the repo owner/name to any value they want and the server will return information on this repo.</p> <p>`DeleteRepositoryByName` uses the same query and I have been able to delete another user&#39;s repo using this technique.</p> <p>The `GetArtifactByName` endpoint also uses this DB query. I have not reproduced the behaviour with this endpoint due to a lack of a suitable test case, but I do not see anything in the implementation of the endpoint to prevent it being exploited.</p> <p>### PoC</p> <p>Setup: 1. Fresh provider/project on the production minder instance which is owned by me. 2. A repo registered by another user (in this case, Ozz)</p> <p>``` # show my identity $ minder auth whoami No config file present, using default values.</p> <p>Here are your details:</p> <p>+----------------------------------------------------+----------------…</p> <p><strong>Affected:</strong> Go: github.com/stacklok/minder</p> <p>### Summary A Minder user can use the endpoints listed in the issue title to access any repository in the DB, irrespective of who owns the repo and any permissions that user may have. ### Details</p> <p>https://github.com/stacklok/minder/blob/e88e4b286e4bc04c03b0332a77961f085e1aa77f/database/query/repositories.sql#L22-L23 https://github.com/stacklok/minder/blob/a115c8524fbd582b2b277eaadce024bebbded508/internal/controlplane/handlers_repositories.go#L277-L278</p> <p>The DB query used here checks by repo owner, repo name and provider name (which is always &#34;github&#34;). These query values are not distinct for the particular user - as long as the user has valid credentials and a provider, they can set the repo owner/name to any value they want and the server will return information on this repo.</p> <p>`DeleteRepositoryByName` uses the same query and I have been able to delete another user&#39;s repo using this technique.</p> <p>The `GetArtifactByName` endpoint also uses this DB query. I have not reproduced the behaviour with this endpoint due to a lack of a suitable test case, but I do not see anything in the implementation of the endpoint to prevent it being exploited.</p> <p>### PoC</p> <p>Setup: 1. Fresh provider/project on the production minder instance which is owned by me. 2. A repo registered by another user (in this case, Ozz)</p> <p>``` # show my identity $ minder auth whoami No config file present, using default values.</p> <p>Here are your details:</p> <p>+----------------------------------------------------+----------------…</p> https://cve.radiocsirt.org/vuln/ghsa-v627-69v2-xx37 https://cve.radiocsirt.org/vuln/gsd-2024-27916 gsd-2024-27916 https://cve.radiocsirt.org/vuln/gsd-2024-27916