Page 2 of 8 results (0.017 seconds)

CVSS: 3.3EPSS: 0%CPEs: 1EXPL: 0

Cosign provides container signing, verification, and storage in an OCI registry for the sigstore project. Prior to version 1.5.2, Cosign can be manipulated to claim that an entry for a signature exists in the Rekor transparency log even if it doesn't. This requires the attacker to have pull and push permissions for the signature in OCI. This can happen with both standard signing with a keypair and "keyless signing" with Fulcio. If an attacker has access to the signature in OCI, they can manipulate cosign into believing the entry was stored in Rekor even though it wasn't. • https://github.com/sigstore/cosign/commit/96d410a6580e4e81d24d112a0855c70ca3fb5b49 https://github.com/sigstore/cosign/security/advisories/GHSA-ccxc-vr6p-4858 • CWE-295: Improper Certificate Validation •

CVSS: 6.5EPSS: 1%CPEs: 13EXPL: 1

cosign-bin/cosign.cgi in Cosign 2.0.2 and earlier allows remote authenticated users to perform unauthorized actions as an arbitrary user by using CR (\r) sequences in the service parameter to inject LOGIN and REGISTER commands with the desired username. En el cosign-bin/cosign.cgi en Cosign versión 2.0.2 y anteriores permite a los usuarios autenticados remotos realizar acciones no autorizadas como un usuario arbitrario mediante el uso de secuencias CR (\r) en el parámetro service para inyectar los comandos LOGIN y REGISTER con el nombre de usuario deseado. • https://www.exploit-db.com/exploits/29844 http://secunia.com/advisories/24845 http://www.securityfocus.com/archive/1/465386/100/100/threaded http://www.umich.edu/~umweb/software/cosign/cosign-vuln-2007-002.txt http://www.vupen.com/english/advisories/2007/1359 •

CVSS: 7.5EPSS: 4%CPEs: 12EXPL: 1

The CHECK command in Cosign 2.0.1 and earlier allows remote attackers to bypass authentication requirements via CR (\r) sequences in the cosign cookie parameter. El comando CHECK en Cosign 2.0.1 y anterioes permite a atacantes remotos evitar requisitos de validación a través de la secuencia CR (\r) en el parámetro de la cookie cosign. • https://www.exploit-db.com/exploits/29842 http://secunia.com/advisories/24845 http://www.securityfocus.com/archive/1/465386/100/100/threaded http://www.umich.edu/~umweb/software/cosign/cosign-vuln-2007-001.txt http://www.vupen.com/english/advisories/2007/1359 •