Login
Newsletter
Werbung

Sicherheit: Zwei Probleme in gnupg
Aktuelle Meldungen Distributionen
Name: Zwei Probleme in gnupg
ID: FLSA:185355
Distribution: Fedora Legacy
Plattformen: Fedora Core 1, Fedora Core 2, Red Hat Linux 7.3, Red Hat Linux 9, Fedora Core 3
Datum: Sa, 13. Mai 2006, 02:58
Referenzen: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-0049
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-0455
Applikationen: The GNU Privacy Guard

Originalnachricht

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0120002802==
Content-type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature";
boundary=------------enig19B0FE837B55EA14040C2968

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig19B0FE837B55EA14040C2968
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

---------------------------------------------------------------------
Fedora Legacy Update Advisory

Synopsis: Updated gnupg package fixes security issues
Advisory ID: FLSA:185355
Issue date: 2006-05-12
Product: Red Hat Linux, Fedora Core
Keywords: Bugfix
CVE Names: CVE-2006-0049 CVE-2006-0455
---------------------------------------------------------------------


---------------------------------------------------------------------
1. Topic:

An updated GnuPG package that fixes signature verification flaws is now
available.

GnuPG is a utility for encrypting data and creating digital signatures.

2. Relevant releases/architectures:

Red Hat Linux 7.3 - i386
Red Hat Linux 9 - i386
Fedora Core 1 - i386
Fedora Core 2 - i386
Fedora Core 3 - i386, x86_64

3. Problem description:

Tavis Ormandy discovered a bug in the way GnuPG verifies
cryptographically signed data with detached signatures. It is possible
for an attacker to construct a cryptographically signed message which
could appear to come from a third party. When a victim processes a GnuPG
message with a malformed detached signature, GnuPG ignores the malformed
signature, processes and outputs the signed data, and exits with status
0, just as it would if the signature had been valid. In this case,
GnuPG's exit status would not indicate that no signature verification
had taken place. This issue would primarily be of concern when
processing GnuPG results via an automated script. The Common
Vulnerabilities and Exposures project assigned the name CVE-2006-0455 to
this issue.

Tavis Ormandy also discovered a bug in the way GnuPG verifies
cryptographically signed data with inline signatures. It is possible for
an attacker to inject unsigned data into a signed message in such a way
that when a victim processes the message to recover the data, the
unsigned data is output along with the signed data, gaining the
appearance of having been signed. The Common Vulnerabilities and
Exposures project assigned the name CVE-2006-0049 to this issue.

Please note that neither of these issues affect the way RPM or up2date
verify RPM package files, nor is RPM vulnerable to either of these
issues.

All users of GnuPG are advised to upgrade to this updated package, which
contains backported patches to correct these issues.

4. Solution:

Before applying this update, make sure all previously released errata
relevant to your system have been applied.

To update all RPMs for your particular architecture, run:

rpm -Fvh [filenames]

where [filenames] is a list of the RPMs you wish to upgrade. Only those
RPMs which are currently installed will be updated. Those RPMs which
are not installed but included in the list will not be updated. Note
that you can also use wildcards (*.rpm) if your current directory *only*
contains the desired RPMs.

Please note that this update is also available via yum and apt. Many
people find this an easier way to apply updates. To use yum issue:

yum update

or to use apt:

apt-get update; apt-get upgrade

This will start an interactive process that will result in the
appropriate RPMs being upgraded on your system. This assumes that you
have yum or apt-get configured for obtaining Fedora Legacy content.
Please visit http://www.fedoralegacy.org/docs for directions on how to
configure yum and apt-get.

5. Bug IDs fixed:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=3D185355

6. RPMs required:

Red Hat Linux 7.3:
SRPM:
http://download.fedoralegacy.org/redhat/7.3/updates/SRPMS/gnupg-1.0.7-13.=
3.legacy.src.rpm

i386:
http://download.fedoralegacy.org/redhat/7.3/updates/i386/gnupg-1.0.7-13.3=
=2Elegacy.i386.rpm

Red Hat Linux 9:

SRPM:
http://download.fedoralegacy.org/redhat/9/updates/SRPMS/gnupg-1.2.1-9.2.l=
egacy.src.rpm

i386:
http://download.fedoralegacy.org/redhat/9/updates/i386/gnupg-1.2.1-9.2.le=
gacy.i386.rpm

Fedora Core 1:

SRPM:
http://download.fedoralegacy.org/fedora/1/updates/SRPMS/gnupg-1.2.3-2.2.l=
egacy.src.rpm

i386:
http://download.fedoralegacy.org/fedora/1/updates/i386/gnupg-1.2.3-2.2.le=
gacy.i386.rpm

Fedora Core 2:

SRPM:
http://download.fedoralegacy.org/fedora/2/updates/SRPMS/gnupg-1.2.4-2.3.l=
egacy.src.rpm

i386:
http://download.fedoralegacy.org/fedora/2/updates/i386/gnupg-1.2.4-2.3.le=
gacy.i386.rpm

Fedora Core 3:

SRPM:
http://download.fedoralegacy.org/fedora/3/updates/SRPMS/gnupg-1.2.7-1.2.l=
egacy.src.rpm

i386:
http://download.fedoralegacy.org/fedora/3/updates/i386/gnupg-1.2.7-1.2.le=
gacy.i386.rpm

x86_64:
http://download.fedoralegacy.org/fedora/3/updates/x86_64/gnupg-1.2.7-1.2.=
legacy.x86_64.rpm

7. Verification:

SHA1 sum Package Name
---------------------------------------------------------------------

8908e71fbca5c2bae5f3aadd774e42a49a5cb957
redhat/7.3/updates/i386/gnupg-1.0.7-13.3.legacy.i386.rpm
dd9dc31630ca66faffb4f214f425b973cb3212cf
redhat/7.3/updates/SRPMS/gnupg-1.0.7-13.3.legacy.src.rpm
b551dcbc9739ca6af6ca175c61709d5a4209fee6
redhat/9/updates/i386/gnupg-1.2.1-9.2.legacy.i386.rpm
937e799801ee740b3076aaf7bae40aedad8150bf
redhat/9/updates/SRPMS/gnupg-1.2.1-9.2.legacy.src.rpm
69c6c0d7cd4250e7e9ce1dc67ce4f3da3ee3b810
fedora/1/updates/i386/gnupg-1.2.3-2.2.legacy.i386.rpm
b0f065bc8326fdc3f842dbc368be479f5d6b27c0
fedora/1/updates/SRPMS/gnupg-1.2.3-2.2.legacy.src.rpm
4c9c5887459282cf336cc18c161eb3a243ea4b6d
fedora/2/updates/i386/gnupg-1.2.4-2.3.legacy.i386.rpm
ffdee44401e55625c991eb20a6fcf316f0fae7c9
fedora/2/updates/SRPMS/gnupg-1.2.4-2.3.legacy.src.rpm
56347e77b9f310b8b9f13b5105f50720d114660f
fedora/3/updates/i386/gnupg-1.2.7-1.2.legacy.i386.rpm
42858f6256ed2aed3ebacaa1ea948ab245713ad6
fedora/3/updates/x86_64/gnupg-1.2.7-1.2.legacy.x86_64.rpm
66087d787f7707eb181ceff7e37d3f2ca624201a
fedora/3/updates/SRPMS/gnupg-1.2.7-1.2.legacy.src.rpm

These packages are GPG signed by Fedora Legacy for security. Our key is
available from http://www.fedoralegacy.org/about/security.php

You can verify each package with the following command:

rpm --checksig -v <filename>

If you only wish to verify that each package has not been corrupted or
tampered with, examine only the sha1sum with the following command:

sha1sum <filename>

8. References:

http://cve.mitre.org/cgi-bin/cvename.cgi?name=3DCVE-2006-0049
http://cve.mitre.org/cgi-bin/cvename.cgi?name=3DCVE-2006-0455

9. Contact:

The Fedora Legacy security contact is <secnotice@fedoralegacy.org>. More
project details at http://www.fedoralegacy.org

---------------------------------------------------------------------


--------------enig19B0FE837B55EA14040C2968
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFEZS6iLMAs/0C4zNoRAnB8AJ9vp1/TF774buiZAb6a07a+lcuSRgCgs5PR
YchNt5NlENmbGMtoKj5YkKQ=
=Xswb
-----END PGP SIGNATURE-----

--------------enig19B0FE837B55EA14040C2968--


--===============0120002802==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--
Fedora-legacy-announce mailing list
Fedora-legacy-announce@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-legacy-announce
--===============0120002802==--
Pro-Linux
Pro-Linux @Facebook
Neue Nachrichten
Werbung