Approved changes feed: RSS · Atom
cpe:2.3:a:lfprojects:minder:*:*:*:*:*:go:*:*
part: a version: * update: *
| Vendor | Lfprojects (4544abc5-133d-544b-9bd5-895c4c487a16) |
|---|---|
| Product | Minder (6858d456-6892-5b7c-8994-efa7c287868c) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | go |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-27916 |
vulnerable | 2026-06-03 14:55:24.216462 |
`GetRepositoryByName`, `DeleteRepositoryByName` and `GetArtifactByName` allow access of arbitrary repositories in Minder by any authenticated user
HIGH (7.1)
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.
Published: 2024-03-06T20:21:22.125Z
Updated: 2024-08-02T19:39:30.349Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-27093 |
vulnerable | 2026-06-03 14:55:16.600037 |
Minder trusts client-provided mapping from repo name to upstream ID
MEDIUM (4.6)
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.
Published: 2024-02-26T21:57:25.101Z
Updated: 2024-08-27T19:43:28.099Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.