CVE-2024-27093

{"id": "CVE-2024-27093", "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 4.6, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L", "integrityImpact": "LOW", "userInteraction": "REQUIRED", "attackComplexity": "LOW", "availabilityImpact": "LOW", "privilegesRequired": "LOW", "confidentialityImpact": "NONE"}, "impactScore": 2.5, "exploitabilityScore": 2.1}]}, "published": "2024-02-26T22:15:07.113", "references": [{"url": "https://github.com/stacklok/minder/commit/53868a878e93f29c43437f96dbc990b548e48d1d", "source": "security-advisories@github.com"}, {"url": "https://github.com/stacklok/minder/security/advisories/GHSA-q6h8-4j2v-pjg4", "source": "security-advisories@github.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-20"}]}], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "Minder es una plataforma de seguridad de la cadena de suministro de software. En la versi\u00f3n 0.0.31 y anteriores, es posible que un atacante registre un repositorio con un ID ascendente no v\u00e1lido o diferente, lo que hace que Minder informe el repositorio como registrado, pero no solucione ning\u00fan cambio futuro que entre en conflicto con la pol\u00edtica (porque los webhooks para el repositorio no coinciden con ning\u00fan repositorio conocido en la base de datos). Al intentar registrar un repositorio con un ID de repositorio diferente, el proveedor registrado debe tener un administrador en el repositorio nombrado o se producir\u00e1 un error 404. De manera similar, si el token del proveedor almacenado no tiene acceso al repositorio, las soluciones no se aplicar\u00e1n correctamente. Por \u00faltimo, parece que las acciones de conciliaci\u00f3n no se ejecutan contra repos con este tipo de descalce. Esto parece ser principalmente una posible vulnerabilidad de denegaci\u00f3n de servicio. Esta vulnerabilidad est\u00e1 parcheada en la versi\u00f3n 0.20240226.1425+ref.53868a8."}], "lastModified": "2024-02-27T14:20:06.637", "sourceIdentifier": "security-advisories@github.com"}