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

http://security.gentoo.org/

Severity:	normal
Title:	ssl-cert eclass: Certificate disclosure
Date:	03/20/2008
Bugs:	#174759
ID:	200803-30

Synopsis

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

Background

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

Affected packages

Package	Vulnerable	Unaffected	Architecture(s)
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

Description

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).

Impact

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.

Workaround

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

Resolution

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"

References

CVE-2008-1383

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: http://security.gentoo.org/glsa/glsa-200803-30.xml

Concerns?

Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at https://bugs.gentoo.org.