-----BEGIN PGP SIGNED MESSAGE-----

===========================================================================
              AUSCERT External Security Bulletin Redistribution
                             
           ESB-2000.303 -- Microsoft Security Bulletin (MS00-080)
        Patch Available for "Session ID Cookie Marking" Vulnerability
                               24 October 2000

===========================================================================

	AusCERT Security Bulletin Summary
	---------------------------------

Product:                Internet Information Server
Vendor:                 Microsoft
Operating System:	Windows NT
			Windows 2000
Impact:                 Inappropriate Access
Access Required:        Remote

- --------------------------BEGIN INCLUDED TEXT--------------------

- -----BEGIN PGP SIGNED MESSAGE-----

Microsoft Security Bulletin (MS00-080)
- - --------------------------------------

Patch Available for "Session ID Cookie Marking" Vulnerability

Originally posted: October 23, 2000

Summary
=======
Microsoft has released a patch that eliminates a security
vulnerability in Microsoft(r) Internet Information Server. The
vulnerability could allow a malicious user to "hijack" another user's
secure web session, under a very restricted set of  circumstances.

Frequently asked questions regarding this vulnerability
and the patch can be found at
http://www.microsoft.com/technet/security/bulletin/fq00-080.asp

Issue
=====
IIS supports the use of a Session ID cookie to track the current
session identifier for a web session. However, .ASP in IIS  does not
support the creation of secure Session ID cookies as defined in RFC
2109. As a result, secure and non-secure pages  on the same web site
use the same Session ID. If a user initiated a session with a secure
web page, a Session ID cookie would  be generated and sent to the
user, protected by SSL. But if the user subsequently visited a
non-secure page on the same site,  the same Session ID cookie would
be exchanged, this time in plaintext. If a malicious user had
complete control over the  communications channel, he could read the
plaintext Session ID cookie and use it to connect to the user's
session with the  secure page. At that point, he could take any
action on the secure page that the user could take.

The conditions under which this vulnerability could be exploited are
rather daunting. The malicious user would need to have  complete
control over the other user's communications with the web site. Even
then, the malicious user could not make the  initial connection to
the secure page - only the legitimate user could do that. The patch
eliminates the vulnerability by  adding support for secure Session ID
cookies in .ASP pages. (Secure cookies already are supported for all
other types of  cookies, under all other technologies in IIS).

Affected Software Versions
==========================
 - Microsoft Internet Information Server 4.0
 - Microsoft Internet Information Services 5.0

Patch Availability
==================
 - IIS 4.0:
   http://www.microsoft.com/Downloads/Release.asp?ReleaseID=25233
 - IIS 5.0:
   http://www.microsoft.com/Downloads/Release.asp?ReleaseID=25232

Note: The patch installs support for secure Session ID cookies, but
does not enable it for reasons of application  compatibility. As
discussed in the Knowledge Base article, it can be enabled or
disabled on a site-by-site basis.

Note:
 - The IIS 4.0 version of this patch can be installed on Windows
   NT(r) 4.0 systems running Service Pack 6a, and will be included in
   Service Pack 7.
 - The IIS 5.0 version of this patch can be installed on
   Windows(r) 2000 systems with or without Service Pack 1, and will
   be included in Service Pack 2.

Note: Additional security patches are available at the Microsoft
Download Center

More Information
================
Please see the following references for more information related to
this issue.
 - Frequently Asked Questions: Microsoft Security Bulletin MS00-080,
   http://www.microsoft.com/technet/security/bulletin/fq00-080.asp
 - Microsoft Knowledge Base article Q274149 discusses this issue
   and will be available soon.
 - RFC 2109, HTTP State Management,
   http://www.ietf.org/rfc/rfc2109.txt.
 - Microsoft TechNet Security web site,
   http://www.microsoft.com/technet/security/default.asp

Obtaining Support on this Issue
===============================
This is a fully supported patch. Information on contacting Microsoft
Product Support Services is available at
http://support.microsoft.com/support/contact/default.asp.

Acknowledgments
===============
Microsoft thanks ACROS Security (http://www.acros.si/) and Ron Sires
and C. Conrad Cady of Healinx (http://www.healinx.com/)  for
reporting this issue to us and working with us to protect customers.

Revisions
=========
 - October 23, 2000: Bulletin Created.

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

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED
"AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT  DISCLAIMS ALL
WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR  PURPOSE. IN NO EVENT
SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY
DAMAGES WHATSOEVER INCLUDING DIRECT,  INDIRECT, INCIDENTAL,
CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF
MICROSOFT CORPORATION OR ITS  SUPPLIERS HAVE BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION
OR LIMITATION OF  LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES
SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last Updated October 23, 2000


- -----BEGIN PGP SIGNATURE-----
Version: PGP Personal Privacy 6.5.3

iQEVAwUBOfT80o0ZSRQxA/UrAQHKGgf7BBNBM8b4gQwlbVBJAeRh8deRWqksPhCv
QKzFVQI11yzGF2jB0hEScFM4GygBjGshigHRa18fO/Op+AKseiIK9xkTAlm/RpEd
epRC4M4lj6YGqMQpJ4uk4ovyWWdL/ZxQcEzDqCGUvckniRUlPI4A6j+3F+igzdFC
Apqdu3I7V46Dp0qMHGRZ65uSoepbXPepQ2igy1REyIAUuBndBZR+FfP/U/8QM/t3
aY6FObaQqMorTmKX0FqKxLXV5uyPIJeZGzkMtU/falik7yEpEXrpJqg/+GHAfkUY
0J0wH4m1qURenKj5GPUapVlm4FQJ0hUEcN6U3k0O3UsOpGj3tciSTg==
=rzSg
- -----END PGP SIGNATURE-----

- --------------------------END INCLUDED TEXT--------------------

This security bulletin is provided as a service to AusCERT's members.  As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content.  The decision to use any or all of this information is
the responsibility of each user or organisation, and should be done so in
accordance with site policies and procedures.

NOTE: This is only the original release of the security bulletin.  It may
not be updated when updates to the original are made.  If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the original authors to ensure that the information is still current.

Contact information for the authors of the original document is included
in the Security Bulletin above.  If you have any questions or need further
information, please contact them directly.

Previous advisories and external security bulletins can be retrieved from:

	http://www.auscert.org.au/Information/advisories.html

If you believe that your system has been compromised, contact AusCERT or
your representative in FIRST (Forum of Incident Response and Security
Teams).

Internet Email: auscert@auscert.org.au
Facsimile:	(07) 3365 7031
Telephone:	(07) 3365 4417 (International: +61 7 3365 4417)
		AusCERT personnel answer during Queensland business hours
		which are GMT+10:00 (AEST).
		On call after hours for emergencies.


-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv
Comment: ftp://ftp.auscert.org.au/pub/auscert/AUSCERT_PGP.key

iQCVAwUBOlSNESh9+71yA2DNAQHmpAP/f2aGaf+vbYiODL89ee8fZGIKuOl66hwK
OrOboJgIkG8gewt6YK+uPE8eKc3aKoEpCvv8L30aoy5xsAMmlJnSC17uuAMslnHn
Z2ZcvTFzgE8gIBZG7NaOSA23WMQmZoI032E+9wCixMmkhkFFOhAU1PI2iFOeMA1m
i6hsGMHuCyQ=
=30Ut
-----END PGP SIGNATURE-----