CVE-2024-27093: Minder trusts client-provided mapping from repo name to upstream ID

Published Feb 26, 2024
·
Updated

Summary

When using a modified client or the grpc interface directly, the RegisterRepository call accepts both the repository owner / repo and the repoid. 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" # repoid is defaulted to 0 }

I was able to produce the following minder output:

+--------------------------------------+--------------------------------------+----------+-------------+-------------------+------------+ | ID | PROJECT | PROVIDER | UPSTREAM ID | OWNER | NAME | +--------------------------------------+--------------------------------------+----------+-------------+-------------------+------------+ | da3acba4-ef66-4d9b-b41e-250869107fd5 | f9f4aef0-74af-4909-a0c3-0e8ac7fbc38d | github | 0 | Stacklok-Demo-Org | python-app | +--------------------------------------+--------------------------------------+----------+-------------+-------------------+------------+ | 7cf8f7b8-b19b-40dd-a96b-b88bb1ef5563 | f9f4aef0-74af-4909-a0c3-0e8ac7fbc38d | github | 762029128 | evankanderson | bad-python | +--------------------------------------+--------------------------------------+----------+-------------+-------------------+------------+

$ gh api repos/Stacklok-Demo-Org/python-app | jq .id 762029128

I've registered bad-python with the ID of python-app, and python-app with an ID of 0.

Impact

This appears to primarily be a potential denial-of-service vulnerability.

Other sources

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.

MITRE

Affected Software

2 affected componentsFixes available
go/github.com/stacklok/minder<0.20240226.1425
0.20240226.1425
Lfprojects Minder Go<=0.0.31

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade go/github.com/stacklok/minder to a version that resolves this vulnerability.

    Fixed in 0.20240226.1425
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 0.20240226.1425+ref.53868a8
  3. Compensating control

    When registering repositories via the normal client/RPC, ensure the repository registration uses the correct upstream repo ID for the given owner/repo mapping; if a mismatch is detected, prevent registration/remediation paths (e.g., avoid modified clients/unauthorized RegisterRepository calls that allow setting an invalid or differing upstream ID).

Event History

Feb 26, 2024
CVE Published
via MITRE·09:57 PM
Data Sourced
via MITRE·09:57 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·10:15 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-27093?

The severity of CVE-2024-27093 has not been explicitly rated, but it poses a significant risk due to improper validation in the registration process.

2

How do I fix CVE-2024-27093?

To fix CVE-2024-27093, update to the latest version of the affected software, ensuring you are beyond version 0.20240226.1425.

3

What systems are affected by CVE-2024-27093?

CVE-2024-27093 affects the GitHub repository 'github.com/stacklok/minder' and versions up to 0.20240226.1425.

4

What is the vulnerability in CVE-2024-27093?

CVE-2024-27093 involves a lack of validation in the 'RegisterRepository' call, allowing mismatched repository parameters to be registered.

5

Can CVE-2024-27093 lead to data breaches?

Yes, due to improper checks, CVE-2024-27093 can facilitate unauthorized access or manipulation of repository data.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203