https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 09:59:19 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-160175 EUVD-2026-160175 https://cve.radiocsirt.org/vuln/euvd-2026-160175 https://cve.radiocsirt.org/vuln/fkie_cve-2024-27093 <p>Minder is a Software Supply Chain Security Platform. In version 0.0.31 and earlier, it is possible for an attacker to register a repository with a invalid or differing upstream ID, which causes Minder to report the repository as registered, but not remediate any future changes which conflict with policy (because the webhooks for the repo do not match any known repository in the database). When attempting to register a repo with a different repo ID, the registered provider must have admin on the named repo, or a 404 error will result. Similarly, if the stored provider token does not have repo access, then the remediations will not apply successfully. Lastly, it appears that reconciliation actions do not execute against repos with this type of mismatch. This appears to primarily be a potential denial-of-service vulnerability. This vulnerability is patched in version 0.20240226.1425+ref.53868a8.</p> <p>Minder is a Software Supply Chain Security Platform. In version 0.0.31 and earlier, it is possible for an attacker to register a repository with a invalid or differing upstream ID, which causes Minder to report the repository as registered, but not remediate any future changes which conflict with policy (because the webhooks for the repo do not match any known repository in the database). When attempting to register a repo with a different repo ID, the registered provider must have admin on the named repo, or a 404 error will result. Similarly, if the stored provider token does not have repo access, then the remediations will not apply successfully. Lastly, it appears that reconciliation actions do not execute against repos with this type of mismatch. This appears to primarily be a potential denial-of-service vulnerability. This vulnerability is patched in version 0.20240226.1425+ref.53868a8.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-27093 https://cve.radiocsirt.org/vuln/ghsa-q6h8-4j2v-pjg4 <p><strong>Affected:</strong> Go: github.com/stacklok/minder</p> <p>### Summary</p> <p>When using a modified client or the grpc interface directly, the `RegisterRepository` call accepts _both_ the repository owner / repo **and** the repo_id. Furthermore, these two are not checked for matching before registering webhooks and data in the database.</p> <p>### Details</p> <p>It is possible for an attacker to register a repository with a invalid or differing upstream ID, which causes Minder to report the repository as registered, but not remediate any future changes which conflict with policy (because the webhooks for the repo do not match any known repository in the database). When attempting to register a repo with a different repo ID, the registered provider must have admin on the named repo, or a 404 error will result. Similarly, if the stored provider token does not have repo access, then the remediations will not apply successfully. Lastly, it appears that reconciliation actions do not execute against repos with this type of mismatch.</p> <p>### PoC</p> <p>With an RPC like the following text proto:</p> <p>``` context { ... } repository { owner: &#34;Stacklok-Demo-Org&#34; repo: &#34;python-app&#34; # repo_id is defaulted to 0 } ```</p> <p>I was able to produce the following `minder` output:</p> <p>``` +--------------------------------------+--------------------------------------+----------+-------------+-------------------+------------+ | ID | PROJECT | PROVIDER | UPSTREAM ID | OWNER | NAME | +------------------…</p> <p><strong>Affected:</strong> Go: github.com/stacklok/minder</p> <p>### Summary</p> <p>When using a modified client or the grpc interface directly, the `RegisterRepository` call accepts _both_ the repository owner / repo **and** the repo_id. Furthermore, these two are not checked for matching before registering webhooks and data in the database.</p> <p>### Details</p> <p>It is possible for an attacker to register a repository with a invalid or differing upstream ID, which causes Minder to report the repository as registered, but not remediate any future changes which conflict with policy (because the webhooks for the repo do not match any known repository in the database). When attempting to register a repo with a different repo ID, the registered provider must have admin on the named repo, or a 404 error will result. Similarly, if the stored provider token does not have repo access, then the remediations will not apply successfully. Lastly, it appears that reconciliation actions do not execute against repos with this type of mismatch.</p> <p>### PoC</p> <p>With an RPC like the following text proto:</p> <p>``` context { ... } repository { owner: &#34;Stacklok-Demo-Org&#34; repo: &#34;python-app&#34; # repo_id is defaulted to 0 } ```</p> <p>I was able to produce the following `minder` output:</p> <p>``` +--------------------------------------+--------------------------------------+----------+-------------+-------------------+------------+ | ID | PROJECT | PROVIDER | UPSTREAM ID | OWNER | NAME | +------------------…</p> https://cve.radiocsirt.org/vuln/ghsa-q6h8-4j2v-pjg4 https://cve.radiocsirt.org/vuln/gsd-2024-27093 gsd-2024-27093 https://cve.radiocsirt.org/vuln/gsd-2024-27093