4 results (0.005 seconds)

CVSS: 5.0EPSS: 0%CPEs: 24EXPL: 0

gpg in GnuPG before 1.4.2.2 does not properly verify non-detached signatures, which allows attackers to inject unsigned data via a data packet that is not associated with a control packet, which causes the check for concatenated signatures to report that the signature is valid, a different vulnerability than CVE-2006-0455. • ftp://patches.sgi.com/support/free/security/advisories/20060401-01-U http://lists.gnupg.org/pipermail/gnupg-announce/2006q1/000216.html http://lists.suse.de/archive/suse-security-announce/2006-Mar/0003.html http://secunia.com/advisories/19173 http://secunia.com/advisories/19197 http://secunia.com/advisories/19203 http://secunia.com/advisories/19231 http://secunia.com/advisories/19232 http://secunia.com/advisories/19234 http://secunia.com/advisories/19244 http://secunia.com/ •

CVSS: 4.6EPSS: 0%CPEs: 23EXPL: 2

gpgv in GnuPG before 1.4.2.1, when using unattended signature verification, returns a 0 exit code in certain cases even when the detached signature file does not carry a signature, which could cause programs that use gpgv to assume that the signature verification has succeeded. Note: this also occurs when running the equivalent command "gpg --verify". gpgv en GnuPG en versiones anteriores a 1.4.2.1, cuando se utiliza verificación de firma desatendida, devuelve un código de salida 0 en algunos casos, incluso cuando el archivo de firma acompañante no lleva una firma, esto puede provocar que los programas que usen gpgv asuman que la verificación de la firma ha tenido éxito. Nota: Esto también ocurre cuando se ejecuta el comando equivalente "gpg --verify". • https://www.exploit-db.com/exploits/27231 ftp://patches.sgi.com/support/free/security/advisories/20060401-01-U http://fedoranews.org/updates/FEDORA-2006-116.shtml http://lists.gnupg.org/pipermail/gnupg-announce/2006q1/000211.html http://marc.info/?l=gnupg-devel&m=113999098729114&w=2 http://secunia.com/advisories/18845 http://secunia.com/advisories/18933 http://secunia.com/advisories/18934 http://secunia.com/advisories/18942 http://secunia.com/advisories/18955 http://sec •

CVSS: 5.0EPSS: 1%CPEs: 12EXPL: 0

GnuPG (GPG) 1.0.2, and other versions up to 1.2.3, creates ElGamal type 20 (sign+encrypt) keys using the same key component for encryption as for signing, which allows attackers to determine the private key from a signature. GnuPG (GPG) 1.0.2 y otras versiones anteriores a 1.2.3 crea claves firma+cifra ElGamal usando el mismo componente para cifrado y para firma, lo que permite a atacantes determinar la clave privada a partir de una firma. • ftp://patches.sgi.com/support/free/security/advisories/20040202-01-U.asc http://distro.conectiva.com.br/atualizacoes/?id=a&anuncio=000798 http://lists.gnupg.org/pipermail/gnupg-announce/2003q4/000276.html http://lists.gnupg.org/pipermail/gnupg-announce/2003q4/000277.html http://marc.info/?l=bugtraq&m=106995769213221&w=2 http://secunia.com/advisories/10304 http://secunia.com/advisories/10349 http://secunia.com/advisories/10399 http://secunia.com/advisories/10400 http://www. •

CVSS: 10.0EPSS: 17%CPEs: 1EXPL: 0

The key validation code in GnuPG before 1.2.2 does not properly determine the validity of keys with multiple user IDs and assigns the greatest validity of the most valid user ID, which prevents GnuPG from warning the encrypting user when a user ID does not have a trusted path. El código de validación de claves en GnuPG 1.2.2 no determina adecuadamente la validez de claves con múltiples IDs de usuario y asigna la máxima validez (de la ID de usuario más válida), lo que impide que GnuPG advierta cuando algunas de las ID no tengan un "trusted path". • http://distro.conectiva.com.br/atualizacoes/?id=a&anuncio=000694 http://marc.info/?l=bugtraq&m=105215110111174&w=2 http://marc.info/?l=bugtraq&m=105301357425157&w=2 http://marc.info/?l=bugtraq&m=105311804129104&w=2 http://marc.info/? •