GLSA 200803-30: ssl-cert eclass: Certificate disclosure

http://security.gentoo.org/

Опасность:	средняя
Заголовок:	ssl-cert eclass: Certificate disclosure
Дата:	20.03.2008
Ошибки:	#174759
ID:	200803-30

Сводка

An error in the usage of the ssl-cert eclass within multiple ebuilds might allow for disclosure of generated SSL private keys.

Назначение

The ssl-cert eclass is a code module used by Gentoo ebuilds to generate SSL certificates.

Уязвимые пакеты

Пакет	Уязвимый	Нетронутый	Архитектура(ы)
app-admin/conserver	< 8.1.16	>= 8.1.16	All supported architectures
mail-mta/postfix	< 2.4.6-r2	>= 2.4.6-r2	All supported architectures
net-ftp/netkit-ftpd	< 0.17-r7	>= 0.17-r7	All supported architectures
net-im/ejabberd	< 1.1.3	>= 1.1.3	All supported architectures
net-irc/unrealircd	< 3.2.7-r2	>= 3.2.7-r2	All supported architectures
net-mail/cyrus-imapd	< 2.3.9-r1	>= 2.3.9-r1	All supported architectures
net-mail/dovecot	< 1.0.10	>= 1.0.10	All supported architectures
net-misc/stunnel	< 4.21-r1	>= 4.21-r1	All supported architectures
net-nntp/inn	< 2.4.3-r1	>= 2.4.3-r1	All supported architectures

Описание

Robin Johnson reported that the docert() function provided by ssl-cert.eclass can be called by source building stages of an ebuild, such as src_compile() or src_install(), which will result in the generated SSL keys being included inside binary packages (binpkgs).

Воздействие

A local attacker could recover the SSL keys from publicly readable binary packages when "emerge" is called with the "--buildpkg (-b)" or "--buildpkgonly (-B)" option. Remote attackers can recover these keys if the packages are served to a network. Binary packages built using "quickpkg" are not affected.

Обход

Do not use pre-generated SSL keys, but use keys that were generated using a different Certificate Authority.

Решение

Upgrading to newer versions of the above packages will neither remove possibly compromised SSL certificates, nor old binary packages. Please remove the certificates installed by Portage, and then emerge an upgrade to the package.

All Conserver users should upgrade to the latest version:

    # emerge --sync
    # emerge --ask --oneshot --verbose ">=app-admin/conserver-8.1.16"

All Postfix 2.4 users should upgrade to the latest version:


    # emerge --sync
    # emerge --ask --oneshot --verbose ">=mail-mta/postfix-2.4.6-r2"

All Postfix 2.3 users should upgrade to the latest version:


    # emerge --sync
    # emerge --ask --oneshot --verbose ">=mail-mta/postfix-2.3.8-r1"

All Postfix 2.2 users should upgrade to the latest version:


    # emerge --sync
    # emerge --ask --oneshot --verbose ">=mail-mta/postfix-2.2.11-r1"

All Netkit FTP Server users should upgrade to the latest version:


    # emerge --sync
    # emerge --ask --oneshot --verbose ">=net-ftp/netkit-ftpd-0.17-r7"

All ejabberd users should upgrade to the latest version:


    # emerge --sync
    # emerge --ask --oneshot --verbose ">=net-im/ejabberd-1.1.3"

All UnrealIRCd users should upgrade to the latest version:


    # emerge --sync
    # emerge --ask --oneshot --verbose ">=net-irc/unrealircd-3.2.7-r2"

All Cyrus IMAP Server users should upgrade to the latest version:


    # emerge --sync
    # emerge --ask --oneshot --verbose ">=net-mail/cyrus-imapd-2.3.9-r1"

All Dovecot users should upgrade to the latest version:


    # emerge --sync
    # emerge --ask --oneshot --verbose ">=net-mail/dovecot-1.0.10"

All stunnel 4 users should upgrade to the latest version:


    # emerge --sync
    # emerge --ask --oneshot --verbose ">=net-misc/stunnel-4.21"

All InterNetNews users should upgrade to the latest version:


    # emerge --sync
    # emerge --ask --oneshot --verbose ">=net-nntp/inn-2.4.3-r1"

Ссылки

CVE-2008-1383

Наличие

Этот GLSA и любые обновления для нее доступны для просмотра на сайте Gentoo Security: http://security.gentoo.org/glsa/glsa-200803-30.xml

Опасения?

Безопасность является одной из главных задач Gentoo Linux и первостепенное значение обеспечить конфиденциальность и безопасность машин наших пользователей. Любые соображения безопасности должны быть адресованы security@gentoo.org или в качестве альтернативы, вы можете сообщить об ошибке на https://bugs.gentoo.org.