Question Locked

How to patch MSMQ vulnerability that should have been fixed with KB892944?

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have an issue related to a Microsoft Security patch. I have several hundred Windows XP machines that are at the most current patch level. All appropriate Windows updates have been applied. I ran an internal vulnerability scan and found that all of my machines are vulnerable to a flaw that was supposed to be fixed by KB892944. This flaw should only affect machines pre Service pack 2 without the noted KB applied. I have downloaded the noted KB and have tried to install it, but I receive an error that my current service pack level is newer than the update. What options do I have to get this vulnerability patched? Thank you for any assistance and let me know if there is any further informatio that would be helpful.

8 replies

by rebelleader

Looking at the contents of the extracted update, there are 8 .DLLs and 1 .SYS file that look like they apply to my issue.

I guess I can try to put these files into their proper locations, register them and see if the issue is corrected.

I am going to have to do a fair amount of QA testing on my test equipment to be certain that this does not break anything.

Thank you for the quick response.

by rebelleader

After looking more at depth into the properties of the DLLs, thones that are currently in use on my systems are considerably newer than the ones included in the updates. I will not be applying the DLLs manually.

by rebelleader

I am currently at SP3 and I understand that the MSMQ vulnerability had been addressed. My internal vulnerability scan however still shows a security hole in MSMQ and notes the patch as the fix for the problem. I use WSUS to manage my Windows updates and have verified that every update that Microsoft thinks my machines need have been applied.

by oh smeg

I would ignore it for the time being and ask M$ Directly on your Usual Channel Account as to what to make of this Message/Report.

Col

by rebelleader

I thought that might be the case as well. To test I turned off the MSMQ service and ran my test again. The machine tested clean. When I turned the service back on and ran the test, the vulnerability was back. The problem looks to really be present.

I do not have the luxury to ignore it as this flaw will cause me to fail a security audit that I am going to be going through in the next few months. I will contact Microsoft to discuss this problem, but am still open to any other suggestions from the community.

Thank you again for assisting.

This discussion is closed to new replies.