-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                freeradius
        Announcement ID:        SUSE-SA:2006:019
        Date:                   Tue, 28 Mar 2006 11:00:00 +0000
        Affected Products:      SUSE LINUX 10.0
                                SUSE LINUX 9.3
                                SUSE LINUX 9.2
                                SUSE LINUX 9.1
                                SUSE SLES 9
        Vulnerability Type:     remote code execution
        Severity (1-10):        7
        SUSE Default Package:   no
        Cross-References:       CVE-2006-1354

    Content of This Advisory:
        1) Security Vulnerability Resolved:
             freeradius input validation problem
           Problem Description
        2) Solution or Work-Around
        3) Special Instructions and Notes
        4) Package Location and Checksums
        5) Pending Vulnerabilities, Solutions, and Work-Arounds:
            See SUSE Security Summary Report.
        6) Authenticity Verification and Additional Information

______________________________________________________________________________

1) Problem Description and Brief Discussion

   Insufficient input validation was being done in the EAP-MSCHAPv2
   state machine of the FreeRADIUS authentication server.

   A malicious attacker could manipulate their EAP-MSCHAPv2 client state
   machine to potentially convince the server to bypass authentication
   checks. This bypassing could also result in the server crashing.

   This is tracked by the Mitre CVE ID CVE-2006-1354.

2) Solution or Work-Around

   There is no known workaround, please install the update packages.

3) Special Instructions and Notes

   None.

4) Package Location and Checksums

   The preferred method for installing security updates is to use the YaST
   Online Update (YOU) tool. YOU detects which updates are required and
   automatically performs the necessary steps to verify and install them.
   Alternatively, download the update packages for your distribution manually
   and verify their integrity by the methods listed in Section 6 of this
   announcement. Then install the packages using the command

     rpm -Fhv 

   to apply the update, replacing  with the filename of the
   downloaded RPM package.


   x86 Platform:

   SUSE LINUX 10.0:
             83c50d73afb03719528c847424179d54

   SUSE LINUX 9.3:
             0bdb0b07c252fc2a6014f30a3898c4e9

   SUSE LINUX 9.2:
             e28918518daba17fb32685179b3cee20

   SUSE LINUX 9.1:
             9dcb23e71a735ce675f349f673c5441e

   Power PC Platform:

   SUSE LINUX 10.0:
             7a4dc1e235c9f9dee719b1350044940f

   x86-64 Platform:

   SUSE LINUX 10.0:
             998a259dc0adf00b33bd78807785aaae

   SUSE LINUX 9.3:
             c73ebda9ead7bc7fa97bc3de2886350f

   SUSE LINUX 9.2:
             a60e2a98d954a9505dfba503ec0351c5

   SUSE LINUX 9.1:
             d02d45273ed3f2c58f5fd014f80efef6

   Sources:

   SUSE LINUX 10.0:
             0eee0bad3d082a2abe180744296e4826

   SUSE LINUX 9.3:
             0992254448350dce633cdac1f3ec4349

   SUSE LINUX 9.2:
             88142a6e271d6319d2cc86745399a578

   SUSE LINUX 9.1:
             5f75a329ee103fbb59e51d6b5a883d87
             b96eadb419be2b7288e48d6b58ea7e0b

   Our maintenance customers are notified individually. The packages are
   offered for installation from the maintenance web:

   
______________________________________________________________________________

5) Pending Vulnerabilities, Solutions, and Work-Arounds:

   See SUSE Security Summary Report.
______________________________________________________________________________

6) Authenticity Verification and Additional Information

  - Announcement authenticity verification:

    SUSE security announcements are published via mailing lists and on Web
    sites. The authenticity and integrity of a SUSE security announcement is
    guaranteed by a cryptographic signature in each announcement. All SUSE
    security announcements are published with a valid signature.

    To verify the signature of the announcement, save it as text into a file
    and run the command

      gpg --verify 

    replacing  with the name of the file where you saved the
    announcement. The output for a valid signature looks like:

      gpg: Signature made  using RSA key ID 3D25D3D9
      gpg: Good signature from "SuSE Security Team "

    where  is replaced by the date the document was signed.

    If the security team's key is not contained in your key ring, you can
    import it from the first installation CD. To import the key, use the
    command

      gpg --import gpg-pubkey-3d25d3d9-36e12d04.asc

  - Package authenticity verification:

    SUSE update packages are available on many mirror FTP servers all over the
    world. While this service is considered valuable and important to the free
    and open source software community, the authenticity and the integrity of
    a package needs to be verified to ensure that it has not been tampered
    with.

    There are two verification methods that can be used independently from
    each other to prove the authenticity of a downloaded file or RPM package:

    1) Using the internal gpg signatures of the rpm package
    2) MD5 checksums as provided in this announcement

    1) The internal rpm package signatures provide an easy way to verify the
       authenticity of an RPM package. Use the command

        rpm -v --checksig 

       to verify the signature of the package, replacing  with the
       filename of the RPM package downloaded. The package is unmodified if it
       contains a valid signature from build@suse.de with the key ID 9C800ACA.

       This key is automatically imported into the RPM database (on
       RPMv4-based distributions) and the gpg key ring of 'root' during
       installation. You can also find it on the first installation CD and at
       the end of this announcement.

    2) If you need an alternative means of verification, use the md5sum
       command to verify the authenticity of the packages. Execute the command

         md5sum 

       after you downloaded the file from a SUSE FTP server or its mirrors.
       Then compare the resulting md5sum with the one that is listed in the
       SUSE security announcement. Because the announcement containing the
       checksums is cryptographically signed (by security@suse.de), the
       checksums show proof of the authenticity of the package if the
       signature of the announcement is valid. Note that the md5 sums
       published in the SUSE Security Announcements are valid for the
       respective packages only. Newer versions of these packages cannot be
       verified.

  - SUSE runs two security mailing lists to which any interested party may
    subscribe:

    suse-security@suse.com
        -   General Linux and SUSE security discussion.
            All SUSE security announcements are sent to this list.
            To subscribe, send an e-mail to
                .

    suse-security-announce@suse.com
        -   SUSE's announce-only mailing list.
            Only SUSE's security announcements are sent to this list.
            To subscribe, send an e-mail to
                .

    For general information or the frequently asked questions (FAQ),
    send mail to  or
    .

    ====================================================================    SUSE's security contact is  or .
    The  public key is listed below.
    ====================================================================

SuSE: 2006-019: freeradius authentication bypass Security Update

March 28, 2006
Insufficient input validation was being done in the EAP-MSCHAPv2 Insufficient input validation was being done in the EAP-MSCHAPv2 state machine of the FreeRADIUS authentication ser...

Summary


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                freeradius
        Announcement ID:        SUSE-SA:2006:019
        Date:                   Tue, 28 Mar 2006 11:00:00 +0000
        Affected Products:      SUSE LINUX 10.0
                                SUSE LINUX 9.3
                                SUSE LINUX 9.2
                                SUSE LINUX 9.1
                                SUSE SLES 9
        Vulnerability Type:     remote code execution
        Severity (1-10):        7
        SUSE Default Package:   no
        Cross-References:       CVE-2006-1354

    Content of This Advisory:
        1) Security Vulnerability Resolved:
             freeradius input validation problem
           Problem Description
        2) Solution or Work-Around
        3) Special Instructions and Notes
        4) Package Location and Checksums
        5) Pending Vulnerabilities, Solutions, and Work-Arounds:
            See SUSE Security Summary Report.
        6) Authenticity Verification and Additional Information

______________________________________________________________________________

1) Problem Description and Brief Discussion

   Insufficient input validation was being done in the EAP-MSCHAPv2
   state machine of the FreeRADIUS authentication server.

   A malicious attacker could manipulate their EAP-MSCHAPv2 client state
   machine to potentially convince the server to bypass authentication
   checks. This bypassing could also result in the server crashing.

   This is tracked by the Mitre CVE ID CVE-2006-1354.

2) Solution or Work-Around

   There is no known workaround, please install the update packages.

3) Special Instructions and Notes

   None.

4) Package Location and Checksums

   The preferred method for installing security updates is to use the YaST
   Online Update (YOU) tool. YOU detects which updates are required and
   automatically performs the necessary steps to verify and install them.
   Alternatively, download the update packages for your distribution manually
   and verify their integrity by the methods listed in Section 6 of this
   announcement. Then install the packages using the command

     rpm -Fhv 

   to apply the update, replacing  with the filename of the
   downloaded RPM package.


   x86 Platform:

   SUSE LINUX 10.0:
             83c50d73afb03719528c847424179d54

   SUSE LINUX 9.3:
             0bdb0b07c252fc2a6014f30a3898c4e9

   SUSE LINUX 9.2:
             e28918518daba17fb32685179b3cee20

   SUSE LINUX 9.1:
             9dcb23e71a735ce675f349f673c5441e

   Power PC Platform:

   SUSE LINUX 10.0:
             7a4dc1e235c9f9dee719b1350044940f

   x86-64 Platform:

   SUSE LINUX 10.0:
             998a259dc0adf00b33bd78807785aaae

   SUSE LINUX 9.3:
             c73ebda9ead7bc7fa97bc3de2886350f

   SUSE LINUX 9.2:
             a60e2a98d954a9505dfba503ec0351c5

   SUSE LINUX 9.1:
             d02d45273ed3f2c58f5fd014f80efef6

   Sources:

   SUSE LINUX 10.0:
             0eee0bad3d082a2abe180744296e4826

   SUSE LINUX 9.3:
             0992254448350dce633cdac1f3ec4349

   SUSE LINUX 9.2:
             88142a6e271d6319d2cc86745399a578

   SUSE LINUX 9.1:
             5f75a329ee103fbb59e51d6b5a883d87
             b96eadb419be2b7288e48d6b58ea7e0b

   Our maintenance customers are notified individually. The packages are
   offered for installation from the maintenance web:

   
______________________________________________________________________________

5) Pending Vulnerabilities, Solutions, and Work-Arounds:

   See SUSE Security Summary Report.
______________________________________________________________________________

6) Authenticity Verification and Additional Information

  - Announcement authenticity verification:

    SUSE security announcements are published via mailing lists and on Web
    sites. The authenticity and integrity of a SUSE security announcement is
    guaranteed by a cryptographic signature in each announcement. All SUSE
    security announcements are published with a valid signature.

    To verify the signature of the announcement, save it as text into a file
    and run the command

      gpg --verify 

    replacing  with the name of the file where you saved the
    announcement. The output for a valid signature looks like:

      gpg: Signature made  using RSA key ID 3D25D3D9
      gpg: Good signature from "SuSE Security Team "

    where  is replaced by the date the document was signed.

    If the security team's key is not contained in your key ring, you can
    import it from the first installation CD. To import the key, use the
    command

      gpg --import gpg-pubkey-3d25d3d9-36e12d04.asc

  - Package authenticity verification:

    SUSE update packages are available on many mirror FTP servers all over the
    world. While this service is considered valuable and important to the free
    and open source software community, the authenticity and the integrity of
    a package needs to be verified to ensure that it has not been tampered
    with.

    There are two verification methods that can be used independently from
    each other to prove the authenticity of a downloaded file or RPM package:

    1) Using the internal gpg signatures of the rpm package
    2) MD5 checksums as provided in this announcement

    1) The internal rpm package signatures provide an easy way to verify the
       authenticity of an RPM package. Use the command

        rpm -v --checksig 

       to verify the signature of the package, replacing  with the
       filename of the RPM package downloaded. The package is unmodified if it
       contains a valid signature from build@suse.de with the key ID 9C800ACA.

       This key is automatically imported into the RPM database (on
       RPMv4-based distributions) and the gpg key ring of 'root' during
       installation. You can also find it on the first installation CD and at
       the end of this announcement.

    2) If you need an alternative means of verification, use the md5sum
       command to verify the authenticity of the packages. Execute the command

         md5sum 

       after you downloaded the file from a SUSE FTP server or its mirrors.
       Then compare the resulting md5sum with the one that is listed in the
       SUSE security announcement. Because the announcement containing the
       checksums is cryptographically signed (by security@suse.de), the
       checksums show proof of the authenticity of the package if the
       signature of the announcement is valid. Note that the md5 sums
       published in the SUSE Security Announcements are valid for the
       respective packages only. Newer versions of these packages cannot be
       verified.

  - SUSE runs two security mailing lists to which any interested party may
    subscribe:

    suse-security@suse.com
        -   General Linux and SUSE security discussion.
            All SUSE security announcements are sent to this list.
            To subscribe, send an e-mail to
                .

    suse-security-announce@suse.com
        -   SUSE's announce-only mailing list.
            Only SUSE's security announcements are sent to this list.
            To subscribe, send an e-mail to
                .

    For general information or the frequently asked questions (FAQ),
    send mail to  or
    .

    ====================================================================    SUSE's security contact is  or .
    The  public key is listed below.
    ====================================================================

References

Severity

Related News