Описание
Sylpheed 2.2.7 and earlier does not properly use the --status-fd argument when invoking GnuPG, which prevents Sylpheed from visually distinguishing between signed and unsigned portions of OpenPGP messages with multiple components, which allows remote attackers to forge the contents of a message without detection.
Sylpheed 2.2.7 and earlier does not properly use the --status-fd argument when invoking GnuPG, which prevents Sylpheed from visually distinguishing between signed and unsigned portions of OpenPGP messages with multiple components, which allows remote attackers to forge the contents of a message without detection.
Ссылки
- https://nvd.nist.gov/vuln/detail/CVE-2007-1267
- http://lists.gnupg.org/pipermail/gnupg-users/2007-March/030514.html
- http://secunia.com/advisories/24414
- http://securityreason.com/securityalert/2353
- http://www.coresecurity.com/?action=item&id=1687
- http://www.securityfocus.com/archive/1/461958/100/0/threaded
- http://www.securityfocus.com/archive/1/461958/30/7710/threaded
- http://www.securityfocus.com/bid/22777
- http://www.securitytracker.com/id?1017727
- http://www.vupen.com/english/advisories/2007/0835
EPSS
CVE ID
Связанные уязвимости
Sylpheed 2.2.7 and earlier does not properly use the --status-fd argument when invoking GnuPG, which prevents Sylpheed from visually distinguishing between signed and unsigned portions of OpenPGP messages with multiple components, which allows remote attackers to forge the contents of a message without detection.
Sylpheed 2.2.7 and earlier does not properly use the --status-fd argument when invoking GnuPG, which prevents Sylpheed from visually distinguishing between signed and unsigned portions of OpenPGP messages with multiple components, which allows remote attackers to forge the contents of a message without detection.
Sylpheed 2.2.7 and earlier does not properly use the --status-fd argum ...
EPSS