Minder trusts client-provided mapping from repo name to upstream ID

Summary 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. Details 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. PoC With an RPC like the following text proto: context { … } repository { owner: "Stacklok-Demo-Org" repo: "python-app" # repo_id is defaulted to 0 } I was able to produce the following minder output: +————————————–+————————————–+———-+————-+——————-+————+ | ID | PROJECT | PROVIDER | UPSTREAM ID | OWNER | NAME |…Read More