There is an URL handling vulnerability potentially allowing remote code execution in Windows XP and Windows Server 2003 systems equipped with Internet Explorer 7. Systems using other Internet Explorer versions seem not to be affected by this bug.
At this moment there is no evidence that this vulnerability has lead to any attack, but Microsoft is investigating the public reports that announced the vulnerability.
Obviously, if confirmed, this vulnerability will be patched as soon as possible by Microsoft.
In the meantime... use Firefox or Opera.
Showing posts with label microsoft bulletin. Show all posts
Showing posts with label microsoft bulletin. Show all posts
Thursday, October 11, 2007
Thursday, September 6, 2007
KB939268: Windows Server 2003 SP1/SP2 stops responding
As specified here, an hotfix is available to resolve one very annoying Windows Server 2003 problem: when the system stops responding but ICMP "ping" works anyway, it COULD be a system process (LSASS.EXE) that stopped working the right way.
The bug affects both SP1 and SP2 patched systems.
The hotfix resolves this situation but must be obtained by contacting the Microsoft Online Customer Services.
The bug affects both SP1 and SP2 patched systems.
The hotfix resolves this situation but must be obtained by contacting the Microsoft Online Customer Services.
Friday, July 13, 2007
The crazy MS07-040 .NET patch
It seems that a recently released Microsoft update for the .NET framework it's acting pretty crazy...
Some users reported very annoying problems due to the installation of this patch: hard-disc trashing, machine performances going down, CPU at 100% for a long while and .NET instability.
Involved technologies are .NET framework 1.0, 1.1 and 2.0.
My advice is to avoid (when suitable) the installation of the patch.
It's more secure to wait until the patch got patched (!).
More detailed infos at this link.
(via Slashdot: "Microsoft .NET Patch May Make PCs Go Haywire")
Some users reported very annoying problems due to the installation of this patch: hard-disc trashing, machine performances going down, CPU at 100% for a long while and .NET instability.
Involved technologies are .NET framework 1.0, 1.1 and 2.0.
My advice is to avoid (when suitable) the installation of the patch.
It's more secure to wait until the patch got patched (!).
More detailed infos at this link.
(via Slashdot: "Microsoft .NET Patch May Make PCs Go Haywire")
Subscribe to:
Posts (Atom)