<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
        {font-family:SimSun;
        panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
        {font-family:"\@SimSun";
        panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman";}
a:link, span.MsoHyperlink
        {color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {color:purple;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal-compose;
        font-family:"Times New Roman";
        color:windowtext;
        font-weight:normal;
        font-style:normal;
        text-decoration:none none;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
        {page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Several modifications have been made to Fixlet content in
the “Enterprise Security” site:<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>1. Microsoft has released a new version of Windows Messenger
5.1. The vulnerability described in security bulletin MS05-009 affects
Windows Messenger 5.0 and is resolved by upgrading to version 5.1. The
action script has been updated to deploy the latest version.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Affected Fixlet message:<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>ID 500903: “MS05-009: Vulnerability in PNG Processing
Could Allow Remote Code Execution - Windows Messenger 5.0”<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>2. Fixlet content for security bulletin MS02-035 on SQL
Server 7.0 has been updated to provide a new action that allows console users
to mark particular computers as fixed.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Affected Fixlet Message:<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>ID 203502: “MS02-035: SQL Server Installation Process
May Leave Passwords on System - SQL Server 7.0”<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>3. Several weeks ago, Fixlet content was updated to account
for the release of Windows Server 2003 SP2. A registry check was added to
existing content to prevent updates from becoming relevant between the time
service pack 2 is installed, and when the machine is rebooted. The
relevance for x64 Windows did not correctly detect the existence of the service
pack in some instances. The relevance has been corrected.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Affected Fixlet IDs:<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>45204, 45205, 45206, 502611, 502614, 502615, 502708, 502709,
503607, 503608, 503609, 503908, 503909, 504007, 504008, 504009, 504108, 504109,
504207, 504208, 504209, 504901, 504902, 504909, 505007, 505008, 505027, 505107,
505108, 505109, 600107, 600108, 600109, 600207, 600208, 600213, 600805, 600806,
600807, 601516, 601517, 601518, 602207, 602208, 602211, 602309, 602310, 602311,
602411, 602412, 602413, 602512, 602523, 602524, 602527, 602528, 603007, 603008,
603207, 603208, 603407, 603408, 603409, 604013, 604014, 604015, 604107, 604108,
604109, 605007, 605008, 605009, 605107, 605108, 605109, 605307, 605308, 605309,
605707, 605708, 605709, 606105, 606106, 606110, 606307, 606308, 606405, 606406,
606407, 606505, 606506, 606507, 606807, 606808, 606809, 607407, 607408, 607409,
607603, 607604, 607610, 607807, 607808, 607811, 607812, 700415, 700416, 700419,
700420, 700605, 700606, 700607, 700807, 700808, 700809, 701107, 701108, 701110,
701215, 701319, 701320, 701321, 701601, 701602, 701603, 701611, 701612<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>BES administrators are encouraged to verify open actions and
synchronize baselines that contain the modified content if appropriate.
Instructions for synchronizing baselines can be found here: <a
href="http://support.bigfix.com/cgi-bin/kbdirect.pl?id=401"
title="blocked::http://support.bigfix.com/cgi-bin/kbdirect.pl?id=401 http://support.bigfix.com/cgi-bin/kbdirect.pl?id=401 blocked::http://support.bigfix.com/cgi-bin/kbdirect.pl?id=401 http://support.bigfix.com/cgi-bin/kbdirect.pl?id=401">http://support.bigfix.com/cgi-bin/kbdirect.pl?id=401</a><font
color=navy><span style='color:navy'>. </span></font>Please contact BigFix
Technical Support if you have any questions regarding this change.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>BigFix Product Team<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Questions / Comments? Use the BigFix User Forum at <a
href="http://forum.bigfix.como/"
title="blocked::http://forum.bigfix.como/ http://forum.bigfix.como/ blocked::http://forum.bigfix.como/ http://forum.bigfix.como/">http://forum.bigfix.com</a><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
</body>
</html>