CVE-2024-29902

{"id": "CVE-2024-29902", "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 4.2, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:N/A:H", "integrityImpact": "NONE", "userInteraction": "REQUIRED", "attackComplexity": "HIGH", "availabilityImpact": "HIGH", "privilegesRequired": "HIGH", "confidentialityImpact": "NONE"}, "impactScore": 3.6, "exploitabilityScore": 0.5}]}, "published": "2024-04-10T23:15:06.920", "references": [{"url": "https://github.com/google/go-containerregistry/blob/a0658aa1d0cc7a7f1bcc4a3af9155335b6943f40/pkg/v1/remote/layer.go#L36-L40", "source": "security-advisories@github.com"}, {"url": "https://github.com/sigstore/cosign/blob/9bc3ee309bf35d2f6e17f5d23f231a3d8bf580bc/pkg/oci/remote/remote.go#L228-L239", "source": "security-advisories@github.com"}, {"url": "https://github.com/sigstore/cosign/commit/629f5f8fa672973503edde75f84dcd984637629e", "source": "security-advisories@github.com"}, {"url": "https://github.com/sigstore/cosign/releases/tag/v2.2.4", "source": "security-advisories@github.com"}, {"url": "https://github.com/sigstore/cosign/security/advisories/GHSA-88jx-383q-w4qc", "source": "security-advisories@github.com"}, {"url": "https://github.com/google/go-containerregistry/blob/a0658aa1d0cc7a7f1bcc4a3af9155335b6943f40/pkg/v1/remote/layer.go#L36-L40", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/sigstore/cosign/blob/9bc3ee309bf35d2f6e17f5d23f231a3d8bf580bc/pkg/oci/remote/remote.go#L228-L239", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/sigstore/cosign/commit/629f5f8fa672973503edde75f84dcd984637629e", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/sigstore/cosign/releases/tag/v2.2.4", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/sigstore/cosign/security/advisories/GHSA-88jx-383q-w4qc", "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-770"}]}], "descriptions": [{"lang": "en", "value": "Cosign provides code signing and transparency for containers and binaries. Prior to version 2.2.4, a remote image with a malicious attachment can cause denial of service of the host machine running Cosign. This can impact other services on the machine that rely on having memory available such as a Redis database which can result in data loss. It can also impact the availability of other services on the machine that will not be available for the duration of the machine denial. The root cause of this issue is that Cosign reads the attachment from a remote image entirely into memory without checking the size of the attachment first. As such, a large attachment can make Cosign read a large attachment into memory; If the attachments size is larger than the machine has memory available, the machine will be denied of service. The Go runtime will make a SigKill after a few seconds of system-wide denial. This issue can allow a supply-chain escalation from a compromised registry to the Cosign user: If an attacher has compromised a registry or the account of an image vendor, they can include a malicious attachment and hurt the image consumer. Version 2.2.4 contains a patch for the vulnerability."}, {"lang": "es", "value": "Cosign proporciona firma de c\u00f3digo y transparencia para contenedores y binarios. Antes de la versi\u00f3n 2.2.4, una imagen remota con un archivo adjunto malicioso pod\u00eda provocar una denegaci\u00f3n de servicio en la m\u00e1quina host que ejecuta Cosign. Esto puede afectar a otros servicios de la m\u00e1quina que dependen de la memoria disponible, como una base de datos de Redis, lo que puede provocar la p\u00e9rdida de datos. Tambi\u00e9n puede afectar la disponibilidad de otros servicios en la m\u00e1quina que no estar\u00e1n disponibles mientras dure la denegaci\u00f3n de la m\u00e1quina. La causa principal de este problema es que Cosign lee el archivo adjunto de una imagen remota completamente en la memoria sin verificar primero el tama\u00f1o del archivo adjunto. Como tal, un archivo adjunto grande puede hacer que Cosign lea un archivo adjunto grande en la memoria; Si el tama\u00f1o de los archivos adjuntos es mayor que la memoria disponible de la m\u00e1quina, se le negar\u00e1 el servicio a la m\u00e1quina. El tiempo de ejecuci\u00f3n de Go realizar\u00e1 un SigKill despu\u00e9s de unos segundos de denegaci\u00f3n en todo el sistema. Este problema puede permitir una escalada de la cadena de suministro desde un registro comprometido hasta el usuario de Cosign: si un adjunto ha comprometido un registro o la cuenta de un proveedor de im\u00e1genes, puede incluir un archivo adjunto malicioso y da\u00f1ar al consumidor de la imagen. La versi\u00f3n 2.2.4 contiene un parche para la vulnerabilidad."}], "lastModified": "2024-11-21T09:08:34.900", "sourceIdentifier": "security-advisories@github.com"}