CVE-2023-46737

{"id": "CVE-2023-46737", "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 3.1, "attackVector": "NETWORK", "baseSeverity": "LOW", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L", "integrityImpact": "NONE", "userInteraction": "REQUIRED", "attackComplexity": "HIGH", "availabilityImpact": "LOW", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 1.4, "exploitabilityScore": 1.6}, {"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.3, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "LOW", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 1.4, "exploitabilityScore": 3.9}]}, "published": "2023-11-07T18:15:09.283", "references": [{"url": "https://github.com/sigstore/cosign/commit/8ac891ff0e29ddc67965423bee8f826219c6eb0f", "tags": ["Patch"], "source": "security-advisories@github.com"}, {"url": "https://github.com/sigstore/cosign/security/advisories/GHSA-vfp6-jrw2-99g9", "tags": ["Exploit", "Vendor Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/sigstore/cosign/commit/8ac891ff0e29ddc67965423bee8f826219c6eb0f", "tags": ["Patch"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/sigstore/cosign/security/advisories/GHSA-vfp6-jrw2-99g9", "tags": ["Exploit", "Vendor Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Modified", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-400"}]}, {"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "CWE-835"}]}], "descriptions": [{"lang": "en", "value": "Cosign is a sigstore signing tool for OCI containers. Cosign is susceptible to a denial of service by an attacker controlled registry. An attacker who controls a remote registry can return a high number of attestations and/or signatures to Cosign and cause Cosign to enter a long loop resulting in an endless data attack. The root cause is that Cosign loops through all attestations fetched from the remote registry in pkg/cosign.FetchAttestations. The attacker needs to compromise the registry or make a request to a registry they control. When doing so, the attacker must return a high number of attestations in the response to Cosign. The result will be that the attacker can cause Cosign to go into a long or infinite loop that will prevent other users from verifying their data. In Kyvernos case, an attacker whose privileges are limited to making requests to the cluster can make a request with an image reference to their own registry, trigger the infinite loop and deny other users from completing their admission requests. Alternatively, the attacker can obtain control of the registry used by an organization and return a high number of attestations instead the expected number of attestations. The issue can be mitigated rather simply by setting a limit to the limit of attestations that Cosign will loop through. The limit does not need to be high to be within the vast majority of use cases and still prevent the endless data attack. This issue has been patched in version 2.2.1 and users are advised to upgrade."}, {"lang": "es", "value": "Cosign es una herramienta de firma de sigstore para contenedores OCI. Cosign es susceptible a una denegaci\u00f3n de servicio por parte de un registro controlado por un atacante. Un atacante que controla un registro remoto puede devolver una gran cantidad de certificaciones y/o firmas a Cosign y hacer que Cosign entre en un bucle largo que resulte en un ataque de datos interminable. La causa principal es que Cosign recorre todas las certificaciones obtenidas del registro remoto en pkg/cosign.FetchAttestations. El atacante necesita comprometer el registro o realizar una solicitud a un registro que controla. Al hacerlo, el atacante debe devolver una gran cantidad de certificaciones en la respuesta a Cosign. El resultado ser\u00e1 que el atacante puede hacer que Cosign entre en un bucle largo o infinito que impedir\u00e1 que otros usuarios verifiquen sus datos. En el caso de Kyvernos, un atacante cuyos privilegios se limitan a realizar solicitudes al cl\u00faster puede realizar una solicitud con una referencia de imagen a su propio registro, desencadenar el bucle infinito y negar que otros usuarios completen sus solicitudes de admisi\u00f3n. Alternativamente, el atacante puede obtener el control del registro utilizado por una organizaci\u00f3n y devolver una gran cantidad de certificaciones en lugar de la cantidad esperada de certificaciones. El problema se puede mitigar simplemente estableciendo un l\u00edmite al l\u00edmite de certificaciones que recorrer\u00e1 Cosign. No es necesario que el l\u00edmite sea alto para estar dentro de la gran mayor\u00eda de los casos de uso y aun as\u00ed evitar ataques interminables a los datos. Este problema se solucion\u00f3 en la versi\u00f3n 2.2.1 y se recomienda a los usuarios que actualicen."}], "lastModified": "2024-11-21T08:29:11.780", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:sigstore:cosign:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "8000584C-3846-4095-9DEE-59F9AE915CF7", "versionEndExcluding": "2.2.1"}], "operator": "OR"}]}], "sourceIdentifier": "security-advisories@github.com"}